esm VS nanoexpress

> I think the biggest miss was not making mixed mode (default) for Node do it the way webpack/babel, etc did it by default in terms of interop. I get they wanted to make it more implicit to call cjs from esm, in the end it just inhibits conversion of existing libraries as dependencies are now a bigger hurdle.

Huge huge agreement.

I forget the specifics but there was some super tiny corner case around maybe default exports that could potentially create ambiguity & that spawned a multi-year bellyaching around doing anything at all for interop. What Node got was incredibly hard fought for against much resistance to interop.

But the final compromises made everything so much more painful for everyone. So many esm projects but oh look a .eslintrc.cjs, how unsurprising & sad.

It's extra maddening because node had a wonderful just works (except that tiny tiny tiny corner case) interop via @standard-things/esm, which seamlessly let the two worlds interop. It'd been around for years before node started shipping support, and it was no ceremony just works bidirectional interoperability, and it took basically no effort or thought from the developers point of view to use. It sucked seeing us walk back from great, mired by frivolous over concern for a obscure corner-case.

https://github.com/standard-things/esm

2) Stay on ES5. Wrap ES6 module(s) with esm adapter. Just like the documentation says:

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: