StreamMinecraftClone VS nanoexpress

This is all that it took me to port a fairly sizeable code base to Linux[0]. This commit allowed me to run the app with the only problem being some font issues that I needed to fix by modifying how I used a library.

The total:

> Showing 26 changed files with 255 additions and 90 deletions.

If you architect your code well, porting between different systems shouldn't take anymore than a few hours ;)

[0]: https://github.com/codingminecraft/StreamMinecraftClone/comm...

Great experience with it. The examples in the repo, the issues and discussions sections, and the documentations are all very helpful. Alex and the other users are also quite hands-on in replying on each and every issue and discussion there.

We have some thin wrapper for uWebSockets.js that lets us do the following:

- parse request json

- parse request multipart data

- serve response json

- serve response buffers

- serve response streams

- serve response static files

- support async handler

- support multiple async handlers (middlewares)

links are here

- https://github.com/joshxyzhimself/modules/blob/main/uwu.mjs

- https://github.com/joshxyzhimself/modules/blob/main/uwu.d.ts

- https://github.com/joshxyzhimself/modules/blob/main/uwu.test...

internally we just serve http, then it goes through caddy or haproxy depending on the project's needs such as tls, caching, etc.

there are other similar projects too that tries to deliver express-like api:

- https://github.com/kartikk221/hyper-express

- https://github.com/nanoexpress/nanoexpress (defunct)

use better performant node framework. (fastify or https://nanoexpress.js.org/ (if it is small app can handle (150k req/s))

Check also https://github.com/nanoexpress/nanoexpress

To demonstrate what I mean, example is-http-code: