api.js | CENNZnet JS API for browsers , React Native and Node.js | Runtime Evironment library

You are creating new socket connection on every useEffect, so after ten messages, you have ten connections.

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.

I encourage you to switch your project to FastAPI, it isn't much different or more difficult than Flask.

FastAPI docs about generating OpenAPI schema

It will not only allow you to generate OpenAPI docs / specification easily. It is also asynchronous, much faster and modern.

See also FastAPI Alternatives, Inspiration and Comparisons to read about differences.

Especially this citation from link above should explain why doing what you try to do may not be the best idea:

Flask REST frameworks

There are several Flask REST frameworks, but after investing the time and work into investigating them, I found that many are discontinued or abandoned, with several standing issues that made them unfit.

The precise location of error properties is not specified. In some environments, it's on the error object itself - in some, it's on the prototype, or is a getter, or something like that.

JSON.stringify will only iterate over enumerable own properties. In Chrome, the .message property is not enumerable, so it won't be included when stringified:

You can use

There is a bug in ForkTsCheckerWebpackPlugin create-react-app (CRA) uses. Updating it to the latest version (at the time of writing 6.2.10) and using this CRA override solves the issue:

From this page of render.com, it looks like they are supporting the latest LTS version: https://render.com/docs/node-version

By default, Render uses the latest LTS version of Node.

Looking at node's current releases: https://nodejs.org/en/about/releases/

It looks like Node.js v14 is the way to go here. You could have your project running locally with Node 10 but if your platform uses 12/14, please try to follow those versions.
As stated in the docs linked above, you can of course set a specific version of Node into .node-version.

(I do also recommend using package.json's engines)

You need to export the function.

Is there any way to keep using a local ("non-global") IOperationFilter (via [SwaggerOperationFilter]) and have my filter injected with dependencies?

Not according to their source code

AnnotationsOperationFilter