I am worried about Bun

butterlesstoast

>Even though I personally am moving some projects away from Bun, don't take my advice as gospel. Always appreciated nuance.

jmuguy

Why did you have to stop using Cursor? I ask this as someone that uses Cursor, but recently at a conference I heard it referred to negatively several times - but in a very vague sense. I don't really have a dog in the fight, I'm using it because thats what the other dev I work with is using.

yabooey

Mostly in my day to day routine, where is use Claude Code maybe 90% of the time, I don’t see that it’s become that bad. Yes they’ve made some questionable decisions on API usage and OpenClaw but I feel like this post is making it out to be worse than it is. That being said I’ve been worried about the future of Bun anyway. Especially if the AI bubble pops. Then again, it’s open source.

james2doyle

Maybe look at https://void.cloud/ (Edit: sorry, meant https://viteplus.dev/ , not Void cloud) They are not a runtime, but they do seem to be interested in wrapping a lot of tools with simple top-level commands

cute_boi

I used to be a fan of Bun, but the way it keeps adding bloat makes me seriously doubt its future. Also, it seems like they are doing a lot of vibe coding without taking enough time, which raises other questions. Node.js is also more stable, and it has started supporting TypeScript out of the box. I don’t think Bun will have many advantages after Node 26.

Sevii

I don't know, I've been using Claude Code since it came out and it really doesn't seem to be getting worse.

AntonyGarand

I disagree with the overall premise: Before the acquisition, Bun had to figure out how to monetize at some point. Now, even though their parent company does some shitty practices with their other software (claude code), it's a stretch to assume this will also translate into making Bun worse: Being worried makes sense but I remain optimistic about Bun. Especially given the context of both of these different context: Claude Code is a gem of Anthropic, experiencing extreme growth and where any of its change can result in billing issues. Bun is a JS runtime, and regardless of its growth, can focus on being the best runtime possible: It doesn't impact billing nor the bottom line of Anthropic, so they don't have to rush out patches due to abuse unlike CC. It's unclear how it will pan out over the next years, still very early on the acquisition to see if anything will change, but I'm not concerned just yet.

the__alchemist

Look at them! They're like loaves of bread that hop.

wxw

> Will we see issues start popping up in Bun that make it seem like the team doesn't even dogfood their own product? I don't know, but I'm not sure I want to continue using it just in case. I sympathize with the general premise. The reaction to move away seems pre-mature though. It sounds like `bun` is still performing just as well as before, and this sentiment isn't based on concrete changes. I also wouldn't expect infrastructure like `bun` to evolve in the way a consumer-facing product, especially one scaling as quickly as Claude Code, can.

b4rtaz__

Personally, I suspect that Bun is a Silicon Valley attempt to lock some companies into its stack (similar to what cloud providers, Next.js + Vercel do). Especially now that Anthropic has become an owner, I'll be keeping Bun at a considerable distance. The funniest part to me is that 10–15 years ago, companies were stuck in the development process due to binary (closed) dependencies. Now they're jumping into the same trap under a different name. Maybe I’ve missed some scandals, but so far OpenJS Foundation is the best thing that has happened for the JavaScript ecosystem.

0sql

Does bun have a formal roadmap? I occasionally see some the changes that Jarred posts on X, and I wonder if they're really meaningful or not (perf improvements are always good). It also seems like a lot of the recent contributions are ai authored. I tried using bun for a project earlier this year and learned that you can't use testcontainers(works fine w/ Deno).

hjort-e

vite and it's ecosystem is actually becoming the unified toolchain with vite+. IIRC pnpm will also be the preferred package manager in the tool

neoden

what a nice way to write an article!

deanc

Let them cook. Anything that they can do to get rid of the absolute hell that is dependencies in the JS ecosystem is worthwhile. I really don't care what they add as long as it's maintained

rtrigoso

I agree with OP, and understand why to some it feels premature. We live in a vastly different world than before, where people are more conscious of ethical concerns and willing to stand on their ground to avoid repeating past mistakes. It might be premature from a tech standard, but it makes sense from an ethical concern. I don't think misconduct is as easily backtracked as it was before and preemptive measures are needed to avoid the large impact that those decisions make.

pyrolistical

I love coding with bun. It comes with everything. For my projects I don’t even need any additional dependencies. I use vanilla dom and sqlite

jonas21

The issues with Claude Code lately look to me like symptoms of being part of a service that is experiencing insane growth (fastest growth in history, by far [1]), while being severely constrained on adding capacity (GPUs are hard to get quickly right now, even if you have the money). I assume they're constantly fighting fires trying to keep the core use cases of Claude Code working, even if that means limiting OpenClaw usage in somewhat draconian ways. It's annoying, but I don't see this as a bad thing at all for Bun. [1] https://www.axios.com/2026/04/13/anthropic-revenue-growth-ai

twoodfin

I’m confident that any unhappiness with Claude Code is at least 95% downstream of Anthropic seeing demand scale their revenue by ~3X in 6 months from a $multi-billion annual base. Their product focus, roadmap, or execution is likely a rounding error in the face of that tsunami. Frankly, it’s shocking they’re doing so well relative to, say, GitHub.

suck-my-spez

I still don't think Bun is production ready. We just ripped bun out of a bunch of our production sevices. CPU runaway and memory leaks. All solved by switching back to nodejs.

pier25

I use Bun and I'm concerned too but it's still too early to tell. Personally my experience with Bun has been 100% positive so far. I'm aware full Node support is not there yet and may never happen but with dependencies that support Bun it's been a smooth ride for me.