Why there's no frameworks or libraries built for bun?
I recently started using bun and completely uninstalled nodejs, npm etc. It super fast. It was launched in 2023. After 3 years why no any powerful libraries build for bun. I use Tanstack Stack and Next.Js. Even though I can create start or next project using…
I recently started using bun and completely uninstalled nodejs, npm etc. It super fast. It was launched in 2023. After 3 years why no any powerful libraries build for bun. I use Tanstack Stack and Next.Js. Even though I can create start or next project using bun, I my projects isn't using the full potential of bun. Still those frameworks install vite, dotenv sql drivers. Just why? Why no libraries out that that uses buns full potential. While I was searching I could find honox, but it's unlikely to modern fullstack frameworks. Bun's framework should be the crown winner because of its power. Why nobody is using it?
Collected discussion
because everyone already uses node and there's no good reason to switch, and now anthropic owns bun which makes its future unpredictable.
The existing Node ecosystem is definitely a big reason. Bun would need to offer something developers cannot easily get with Node before most people would consider switching.
https://bun.com/blog/bun-in-rust Faster, smaller, less bugs... rewritten with preview Fable 5. What's not to like?
It was acquired by Anthropic and completely rewritten in Rust by AI. There's no way I'm putting a service in production using a runtime that a) is owned by an AI company and b) had no human oversight in a complete rewrite that was done in less than 2 weeks. There's no part of that concept that sells me on stability, which is what actual solutions in prod need.
whoa hang on, anthropic owns bun now? i completely missed that, when did that happen that explains a lot though, nobody wants to build on a platform that might get rugpulled or turned into some enterprise-only thing next quarter. i was looking at bun for a side project last month and the speed was genuinely wild but the ecosystem just feels half-finished, like everything's held together with duct tape and a prayer
Partially because post-acquisition Bun has been exclusively utilized as a Claude marketing surface, partially because the Bun philosophy has been that you don't need libraries and that they'd rather build your 'niche' into the runtime itself. The runtime also just doesn't have the market share for many to begin to consider maintaining separate releases that target Bun native features.
Frameworks chase users, not runtimes. Bun being faster is nice, but it has to be boringly compatible before maintainers spend years supporting Bun-only paths. Until then most libs will target Node semantics and let Bun be the drop-in accelerator. Not glamorous, but neither is maintaining two dependency universes.
https://elysiajs.com/ is written for Bun