4 ms·
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 like
by adam_arthur 4y 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.
- nine_k 4y agoI 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.
- adam_arthur 4y agoYeah, a compatibility branch or a build time cross compatibility compiler would suffice.
- Jarred 4y agoWe 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
- petre 4y agoWill 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.