npm-expansions VS npm-run-all

NPM stands for a lot of other things too

Placeholders? In Netlify's case it's likely just some kind of {adjective}-{adjective}-{noun} generator, whereas in NPM's case, it's a list of fun variants: https://github.com/npm/npm-expansions/blob/master/expansions.txt

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?

Finally with help of the run-s cli command we create a build script that runs the command sequentially. So run-s build:* will first run remix build followed by build:css script.

Or, if you don't have bash (Windows for example) you could use a package like Concurrently or NPM-Run-All.

Install the npm-run-all package (if not present)

We can run all these scripts in parallel by using npm-run-all

dev uses npm-run-all to run both commands at the same time, so you don't have to have two terminals open.

Used npm-run-all to enable to run commands for the front-end and back-end at once.

npm-run-all