Server.js | A Triple Pattern Fragments server for Node.js | Runtime Evironment library

You need to quote the *: nodemon -e "*" src/server.js.

Unlike Windows' cmd, Linux shells expand wildcards (as you can see in the command actually run, above the error). In Windows it's up to the program you are calling to expand wildcards. Since that is what you want in case of nodemon, it worked "by chance" on Windows without escaping the asterisk because it doesn't have any special meaning to cmd, but in Linux it will get expanded and that's not what you want.

Mayby you are missing

try npm run build after that you can use npm start. alternatively, if you are developing and are not in production use npm run dev.

So, there are a bunch of ports which are considered unsafe by chrome browser which includes 5060 which you were specifying earlier. That's why earlier you were getting "ERR_UNSAFE_PORT" error when you were trying to load localhost:5060.

From the program perspective, there isn't anything wrong. And at first glance everything will look okay. The problem starts when chrome identifies the port and declares it unsafe. This is done by the browser to prevent XSRF so, that someone doesn't use chrome as a proxy to attack your services.

How do you know which are the ports we are not supposed to use? Refer at this link which provides a list of blocked ports on chrome browser - https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/net/base/port_util.cc

Final program would look like:

Your TEMPLATES setting is as follows (truncated to keep answer short):

The object you want to save

In your userSchema you have defined uid as unique and when you are calling your /test endpoint you are always passing the same uid which is not unique, instead of that use uuid for the uid field.

• Firstly, make sure your server is running on port 5000. You can check it by reading the log Server running on port ...

• Then, you can do a simple test in Postman to make sure the server and the route work correctly.

• If the 2 things above work, this is likely a problem on the client-side for me. Somewhere in your client code, you're sending a request like this :

Well socket objects in nodejs belong to a particular process. You can't just share them with another process easily. If you want one process to cause data to be sent on a socket the other process owns, then send the data itself to the other process using a different server and send some identifier with the data that the receiving process can use to figure out which socket the data should be sent to and it will then send the data over the socket it has. But, this whole thing sounds like a really confusing way to do things.

For example, let's say you have serverTCP (the plain TCP server from your server.js) and serverAPI (an Express server from your other file) each in separate processes. Put a separate Express server in serverTCP running on a local port, not open to the outside world. When serverAPI receives some data for some socketID, it then makes an http request to serverTCP and sends the data and the socketID. serverTCP receives that http request, gets the socketID and the data out of that request and sends it out over the appropriate socket it has a connection to.

FYI, this is generically known as a proxy where your API is somewhat serving as a proxy for the real socket connection. There are all sorts of modules in NPM that implement actual proxies too.