alt Hacker NewsShow HN: Nub – A Bun-like all-in-one toolkit for Node.js
Colin here, creator of Nub. I’ve had the general shape of this in mind for years. Nub runs your code with stock `node`, augmented with a `--require` preload hook[0] that adds a transpiler (oxc-powered, packaged as a Node-API add-on), registers a module resolution hook[1], and injects polyfills as needed for APIs like `Worker`, `Temporal`, etc. All purely additive, your code ultimately runs using Node’s actual engine & stdlib implementations.
[0] https://nodejs.org/api/cli.html#-require-module
[1] https://nodejs.org/api/module.html#moduleregisterhooksoption...
Comments
I’m surprised to see this using a `--require` hook (rather than `--import`). Maybe something’s changed significantly since I was looking into building some similar functionality… but it makes me wonder about nuances in nub’s ESM support.
(When I was investigating this it was very early in Node’s `--import` story, but there were several edge cases with the more common ESM-to-CJS approaches that I wanted to address. Most were probably exceedingly niche concerns, but I’d expect top-level await to affect a meaningful subset of users.)
Hasn't Node been able to run TypeScript for a couple of versions? Why's the transpiler needed?
Just merged a PR migrating our entire monorepo to nub.
0 issues, ridiculously fast.
The readme says Websockets support is native from Node 22, except Node does not have a native Websockets library. Their link for Websockets standard goes to MDN, which is fine except that only describes the WHATWG user interface and nothing about the protocol or how Websockets works.
It feels like this is missing something or using a nonnative library as a supplemental addition.
I actually really like this! Great choices all around.
I saw this on twitter and loved it, such a good move on your part Colin. Hope the project picks up tons of steam!
Respect for embracing existing tech instead of rewriting a worse version of it. Wonder where we would be today if all alternative-building effort went to Node instead (with proper leadership).
Very smart. You can't lose all your customers for vibe-coding a migration to Rust if you are already written in Rust ;)
This looks fantastic.
One suggestion, for package management you should just wrap pnpm, my desire to move to anything else is nil.
I didn't even click on the link. I just came to give the author a hat-tip on the project name. Well played.
Am I expected to be able to run this in production on the backend, or do I still need to transpile and bundle? Do we expect the performance and memory overhead to be negligible. What would be the expectations on terms of added attack surface?
Love the idea, learning a lot of interesting things about node hooks by reading docs and some code
> TypeScript-friendly resolution: extensionless imports, tsconfig.json#paths
I’m wondering how that works. Deno has very complicated import resolution, so building my own import resolver to be compatible with it is a bit of a pain. (This is for a custom lint-like tool.)
I know some people who pronounce n00b like nub, which makes this sort of funny to me. (Maybe it's even intentional?)
Nice, I think this fills a niche. Does it work on cloudflare workers?
- eli 5 : what is so great about this
Nice. Can we get `nub --compile` up in there like Bun has?
There's also the option of using Jiti
It would add an extra dependency though
Will you be able to integrate aube updates after vendoring it? https://github.com/nubjs/nub/pull/81
what's wrong with bun? And how is this better?
[dead]
Very cool idea which makes a lot of sense. Bun provides more (eg db drivers) but the DX is certainly a big part of its appeal.
For reference, the main author of Nub is Colin McDonnell who created Zod and even worked at Bun at some point.