Hacker News new | ask | show | jobs
by adam_arthur 1286 days ago
What's the target level of compatibility with existing npm modules? 100%? Some lower percentile?

Hate to carry forward baggage of past design choices, but likely essential to really get widespread adoption. I'd definitely start using Bun for my projects today (non-production), if it works seamlessly with existing packages.
2 comments
Jarred 1286 days ago
We want Bun to feel more like an upgrade from Node than switching runtimes

Basically everything that doesn’t rely on node’s internal “bindings” C++ stuff should eventually be supported

link
petre 1286 days ago
Will bun perpetuate the dependency hell that it prevalent with node? I like the deno approach better in this regard.

Are there any install methods other than piping curl into bash? Like packages.

link
nine_k 1286 days ago
I suppose a compatibility shim for features that should not go into the new core could work. It would have a performance cost, but as long as this cost is limited to some deprecated APIs it would be OK.
link
adam_arthur 1286 days ago
Yeah, a compatibility branch or a build time cross compatibility compiler would suffice.
link