lora-packet | LoRa radio packet decoder | Messaging library

While Node.JS has several ways for handling circular dependencies, dynamical requires are usually a bad idea - it can create many unpredictable situations. It's best to require all the modules you need and then just use them in emitters.

It's very complicated to try to speak multiple protocols on the same port. It requires some sort of scheme at the beginning of each connection to sample the incoming data and identify which protocol it is and then shunt that connection off to the right code to handle that protocol. I wouldn't suggest it.

It is way, way easier to just open a second server on a different port for an Express server to field your http requests. Very simple. You can do it right in the same app. Because both servers can be in the same app, you can just directly read from one connection and write to the other. There's no need for interprocess communication.

Is there any way that http requests can also be handled by the same server or should I open another port and deploy an express node js app on that?

Open another port. No need to write another app unless you have a specific reason to use two processes. You can put both the plain TCP server and the Express server in the same node.js app.

If I use the same 8080 port for http, how can the routing be achieved?

It's not easy. Not suggest to use the same port for multiple protocols.

If I use different ports for http and raw tcp/ip, what would be the best way for communication between the two server. The communication between tcp/ip server and http server should happen via socket(sending data dynamically).

You can put both servers in the same node.js app and then you can just read/write directly from one to the other with the same code. No need for interprocess communication.

From http server using socket, data has to be sent dynamically to browser to update live location

Sending data dynamically to a browser usually means you want the browser to hold something like a webSocket or socket.io connection to your server so you can then send data to the browser at any time over the existing connection. Otherwise, you would have to "wait" for the browser to request data and then respond with the data when it asks.