[Enhancement] HyperExpress.Response should extend http.ServerResponse about hyper-express HOT 1 CLOSED

So according to the Node.js documentation http.ServerResponse extends http.OutgoingMessage which then extends Stream.

After briefly looking through the docs and messing around with the constructors, It seems that the following is how you would construct an http.ServerResponse instance.

const socket = new net.Socket(); // < This is the problem as the uWS.HttpResponse component is nowhere compatible with a net.Socket
const message = new http.IncomingMessage(socket);
const nodeResponse = new http.ServerResponse(message);
const hyperExpressResponse = new Response(nodeResponse);

The net.Socket component is fairly low level and as you can see there are about two http classes in between that are constructed and extended until you receive an http.ServerResponse. Even if a proper wrapper of net.Socket around uWS.HttpResponse could be written, the overhead of other constructions in between may cause degraded performance without any ability for us to optimize or modify the code of either http.IncomingMessage or http.ServerResponse.

While HyperExpress may present a very familiar API to Express, the underlying logic for processing and handling the network operations through uWS are vastly different from those of the http module. Since requests are essentially a flow of data coming in and going out, the decision was made to only extend Readable / Writable streams and then implement any compatibility methods that all then call the HyperExpress methods under the hood.

If you can come up with a lightweight / practical way to bridge this gap between uWS and Node HTTP further, then I would be glad to accept PRs or recommendations to do so but the above is a general breakdown of the current structure of HyperExpress.

from hyper-express.