concurrently VS public-apis

Before we begin, it's essential to ensure that we have Tailwind CSS and Concurrently installed. Tailwind CSS utility classes will be used for styling our project and will not affect the functionality. Concurrently will allow us to run our React frontend and server file simultaneously on our machines. For now, knowing the purpose that Concurrently serves is enough. We will see how to make it work later in the article.

To efficiently develop and test these applications, it’s essential to run React and Express servers simultaneously. One option is to manually start each server using separate terminal windows or tabs, but this approach is cumbersome and inefficient. An option is to use the concurrently or npm-run-all  CLI tools designed to run multiple npm-scripts in parallel or sequentially.

Let's configure our scripts in the package.json file to launch JSON-Server, to make the process easier we will use Concurrently, an NPM package that allow us to run multiple commands simultaneously.

[1] https://metatype.dev [2] https://github.com/metatypedev/metatype/blob/main/whiz.yaml [3] https://actix.rs/docs/actix/actor/ [4] https://github.com/open-cli-tools/concurrently

Lastly if you want to run your dev build tool and backend as a single command you could try something like pm2 (https://www.npmjs.com/package/pm2) or concurrently (https://www.npmjs.com/package/concurrently). This isn't necessary but might be a nice-to-have. NPM workspaces could help you organize this with a common package.json file too. (https://docs.npmjs.com/cli/v7/using-npm/workspaces)

We attempted to use a combination of tsc --watch, concurrently and Nodemon, but started to run into things breaking left and right, e.g.

Now, the tsconfig.vitest.json seems to be the most "complete" (it will check app files as well as test files), so it's a good choice if you really had to choose one config and run with it (and you still get type checking in the IDE for each config). But, this doesn't include the files from tsconfig.config.json, and as an app grows, the "app" and "vitest" configs may diverge, so wouldn't it be best to use something like concurrently or npm-run-all to run vue-tsc against all 3 configs?

For inspirations on what type of agents I should build, I turned to the Public APIs GitHub repository which has a curated lists of free APIs. I narrowed my search for an API that does not require sign-up or an API key and returns useful information. I ultimately decided to use the Free Currency Exchange Rates API, which seemed promising upon some basic testing.

✅ public-apis/public-apis : https://github.com/public-apis/public-apis

Public-Apis Github Repo — A list of free public APIs.

Interesting thread at https://github.com/public-apis/public-apis/issues/3104

Use curl to access a free public API and get a random joke, cat fact, or whatever.

I remember the forking of https://github.com/public-apis/public-apis and the long git issue discussions. The company owning the repository stopped maintaining it but didn't give up control either. Over the years you've put in a lot of work in publicapis.dev and that is much appreciated.

Also, that isn't really a list of "contributors", but of "organisations with the most stars". Those are different things.

For example "public-apis"[1] didn't "contribute" anything as that's not a person, and looking at GitHub[2] there are a bunch of substantial contributors (the person who created the organisation/repo only has 12 commits by the way);

[1]: https://opensource-heroes.com/o/public-apis

[2]: https://github.com/public-apis/public-apis/graphs/contributo...