webpack-dev-middleware VS concurrently

Are you using webpack? If so, they have a middleware for exactly this case: https://github.com/webpack/webpack-dev-middleware. The example there should be added to your express script with some form of conditional statement to use express.static in your deployment and webpack-dev-middleware in dev.

It looks like this should have been fixed back in 2017: https://github.com/webpack/webpack-dev-middleware/issues/229

Meteor-Webpack integrates webpack-dev-middleware and webpack-hot-middleware to benefit HMR in your project. The only thing you have to do is enabling this feature just like any other Webpack project;

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?