react-server-components-demo VS concurrently

Access the full code for our sample project, or experiment with RSC yourself. For powerful React tools and components, check out GrapeCity's JavaScript solutions.

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: