concurrently VS grpc-dotnet

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:

Official gRPC Repository on GitHub

Given it's a binary serialization framework, it should not be too difficult, because the domain is well-explored and numerous libraries exist in C# which address same goals that Fury does.

More popular/newer examples are https://github.com/Cysharp/MemoryPack (which is similar to Fury with its own spec, C#-code first schema), https://github.com/MessagePack-CSharp/MessagePack-CSharp or even gRPC / Protobuf tooling https://github.com/grpc/grpc-dotnet

And I used Unity because I wanted a tool/engine that I can use to build the game for multiple platforms at once, however, after a while I realized that the game is really simple and I'm not utilizing Unity. Actually, it was quite the opposite, the performance of the game (when it comes to simple animations like drag and drop) was not that good, the size was large, and some tools like gRPC-net are not maintained anymore for Unity.

You can refer to this grpc spa example. It also demonstrates how to use grpc instead of restful API to communicate with dotnet backends.