concurrently VS Nodemon.io

In our demonstration, we use Webpack to build apps and Babel to transpile React code to plain JavaScript. We run our server with Express.js and use concurrently to run multiple commands concurrently. The tool nodemon helps develop node.js-based applications by automatically restarting the node application when file changes in the directory are detected.

It seems like you're trying to solve a developer experience, or DX, problem. I believe the "norm" is to have these scripts run separately, e.g., run npm start and dotnet watch in separate terminals. However, if you want to make it so you don't have to do that, which is fine everyone develops differently, then you could look into concurrently. Then you could add a script to the frontend's package.json like npm start to run concurrently "webpack serve" "dotnet watch".

https://www.npmjs.com/package/concurrently#usage

Another user, /u/jamdatadude, suggested concurrently. I think this can fit your use case here!

I’m no pro at this, but if I remember correctly, you want to build a separate server and client folder and then set up a proxy and use https://www.npmjs.com/package/concurrently

To run both commands, will use the concurrently npm package:

nodemon - enables automatic reload of your server after code change docs

Then, install nodemon (in the VSCode terminal also), which, to my understanding, automatically refreshes the server you'll be sending requests to, whenever you make a change. Using plain node.js, you'd have to manually stop and restart the server after every change.

That's already pretty good, but as you already know it's a PITA to work with this during development. You will have to rebuild your Docker images whenever you change your code, even though your apps will probably support hot-reloading out of the box (or with something like Nodemon if not).

Are you moving your projects to use ES Modules but you are facing some unexpected issues? You are not alone in this fight. In this tutorial, you will learn how to set up nodemon along with ts-node.

We can now use npm run dev to start the server using nodemon, which enables hot refreshing on changes.

Welcome to my blog, where we dive into the intriguing world of Node.js development and tackle one of the common stumbling blocks many developers encounter: the "Nodemon Error - nodemon.ps1 cannot be loaded because running scripts is disabled on this system." If you've ever come across this error while working with Nodemon, fear not! In this article, we will explore the causes behind this issue, understand why scripts are disabled on certain systems and most importantly, provide you with practical solutions to overcome this obstacle and keep your development workflow seamless. So, let's embark on this troubleshooting journey together and empower ourselves to conquer the Nodemon Error!

You’ll need to restart the server using node index.js whenever you change any project file. You can also use Nodemon to automate this.

nodemon will be required to monitor for any changes in our source code and automatically restart our server.