Alternatives
Products that do what Why Node.js libraries aren't promises by default does
- 1AN
2018 · npmjs.com
- 2FP
2019 · github.com
- 3KT
2016 · github.com
- 4DS
2020 · npmjs.com
- 5XA
2015 · github.com
- 6PT
2019 · github.com
- 7EI
2016 · everythingstays.com
- 8SC
2016 · stdlib.com
- 9CF
2016 · github.com
- 10CJ
2019 · github.com
- 11MN
2017 · mrnode.tk
- 12EG
2016 · github.com
- 13AS
2017 · github.com
- 14SJ
2016 · github.com
- 15PO
2013 · github.com
- 16AT
2014 · github.com
- 17NF
2013 · github.com
- 18AN
2016 · github.com
- 19FJ
2011 · firejs.firebase.co
- 20IM
2016 · pesfandiar.com
- 21OJ
2018 · vincit.github.io
- 22LP
2015 · thriqon.github.io
- 23BA
2016 · leanpub.com
- 24CA
I’ve been experimenting with building a Node.js HTTP framework using Rust + Hyper with N-Api. The project started as a fully synchronous server, but I recently patched it to support async (Tokio/Hyper). That change alone nearly doubled throughput in benchmarks. What’s different: * Built directly on Hyper, no heavy abstraction * napi glue for Node.js bindings * Minimal core (sync and async engines side-by-side) * Focused on raw performance, not plugins (yet) This is still experimental and not production-ready. I’d like feedback on: * Async API design — does it feel ergonomic? *…
2025
Ranked by how close each launch is in meaning, then by votes. Refine with a description →