3 Prevalent Themes in the Discussion
| Theme | Supporting Quote |
|---|---|
| 1️⃣ Strong positive reception & rapid adoption | “I saw this on twitter and loved it, such a good move on your part Colin. Hope the project picks up tons of steam!” – awaseem |
| “Just merged a PR migrating our entire monorepo to nub. 0 issues, ridiculously fast.” – ssalbdivad | |
| 2️⃣ Technical curiosity about implementation details | “I’m surprised to see this using a --require hook (rather than --import). Maybe something’s changed significantly … but it makes me wonder about nuances in nub’s ESM support.” – eyelidlessness |
| “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.” – skybrian | |
| 3️⃣ Broader use‑case questions & roadmap interest | “Does it work on docker containers?” – GL26 (answered: “Yep, full support on macOS, Linux, Windows. No official image yet …”) – colinmcd |
“Can we get nub --compile up in there like Bun has?” – montroser (reply: “Coming very soon!”) – colinmcd |
The summary highlights the community’s enthusiasm, the technical questions that arise around hooks and ESM handling, and the interest in extending nub to new environments and future features.