Bun
Fast all-in-one JavaScript and TypeScript runtime, bundler, test runner and package manager.
Liked as a fast, Node-compatible runtime123 with a batteries-included standard library and TypeScript support out of the box.4567 The most common worry is trust after its AI-driven Rust rewrite,89101112 followed by reports of memory issues and bugs that keep some commenters from using it in production.13141516
Why people recommend it
Speed · 3
Commenters describe Bun as fast for builds, running code and on-the-fly code transforms.
“I've been very satisfied since I switched to Bun. It's fast and has a great standard library.”
“I use Bun as a Node.js replacement that works really well.”
Show 1 more
“do it really faster than vite”
Node compatibility · 3
Commenters say it works well with the Node ecosystem and is closer to Node than Deno.
“Bun also had far better compatibility with many libraries & native dependencies”
“Bun feels focused on meeting me where I am.”
Show 1 more
“I use Bun as a Node.js replacement that works really well.”
Standard library · 3
Commenters say built-ins like SQLite, image handling and JSX reduce the need for extra dependencies.
“I love coding with bun. It comes with everything.”
“Bun has been nothing but amazing wins for me”
Show 1 more
“Bun feels focused on meeting me where I am.”
Developer experience · 3
Commenters praise the ease of use, including running TypeScript directly without a compile step.
“Both Bun and Node.js will execute Typescript directly without a compile step.”
Show 1 more
“I use it heavily for personal use and find it works very well and lets me ship small applications quickly.”
Reliability for some · 3
Some daily and production users report few or no regressions.
“I use it daily and I've seen basically zero regressions.”
“Personally my experience with Bun has been 100% positive so far.”
Show 1 more
“Bun feels focused on meeting me where I am.”
Low memory · 3
Commenters say it reduced RAM usage, which helps on budget servers and small VMs.
“Bun also keeps improving at fast pace and constantly reduce memory usage which can be useful on budget server.”
“I use Bun as a Node.js replacement that works really well.”
Show 1 more
“Bun has been nothing but amazing wins for me”
Caveats and dissent
Rewrite trust · 3
The large AI-assisted Rust rewrite left many commenters nervous about code quality and churn.
“the state of the code was very, very bad. There were 13,000 instances of `unsafe`”
“Can the same be said of Bun, which switched to an entirely different language in a single, million-line PR?”
Show 1 more
“I have a long running side project I migrated to bun, and I'm starting to regret it. I don't want to build on top of this much churn.”
Bugs and memory · 3
Commenters report segfaults, use-after-free crashes, memory leaks and backpressure bugs.
“tons of issues appeared. Use-after-free bugs when a client disconnects”
“Nobody is actually running it in production as a runtime. Why? Memory leaks and a whole bunch of other issues.”
Show 1 more
“using Bun as the transpiler+bundler since it's so turnkey, and I ran into a few segfaults”
Production readiness · 2
Some commenters use it for scripts but would not ship a production service on it.
“Nobody is actually running it in production as a runtime. Why? Memory leaks and a whole bunch of other issues.”
Slow fixes · 3
Commenters cite long-open issues and delays in shipping merged fixes, including a security fix.
I love your work on bun. How do you feel about all the constant concerns being raised about the quality of the project lately? I understand some of them might just be typical twitter hate but some of them are real. And I think people are right to question why you are adding image processing or web views inside a javascript runtime when there are bugs affecting production that sit unaddressed. For example on of our bi
“At $work we've been refreshing the Bun release page for days, wondering when they would push the fix.”
Show 1 more
“Until this bug is fixed, there's no trusting Bun”
Feature bloat · 2
Some commenters object to adding features like image processing and web views while bugs remain open.
“the way it keeps adding bloat makes me seriously doubt its future”
I love your work on bun. How do you feel about all the constant concerns being raised about the quality of the project lately? I understand some of them might just be typical twitter hate but some of them are real. And I think people are right to question why you are adding image processing or web views inside a javascript runtime when there are bugs affecting production that sit unaddressed. For example on of our bi
Monorepo lockfile · 1
One commenter could not isolate a single package from the lockfile for Docker builds in monorepos.
“I use bun for everything except for monorepos with isolated deployment targets and shared packages.”
Often compared with
3 moved from Node.js to Bun
1 moved from Deno to Bun
1 moved from Bun to Deno
Who recommends it in their own words
From the makers not counted in the ranking
“I am trying to get Bun running on Win9x”
Threads where it came up
- I am worried about Bun 4 mentions
- Anthropic acquires Bun 4 mentions
- Bun 1.4 Rust rewrite is not looking good 3 mentions
- Bun 1.4 3 mentions
- Claude Code uses Bun written in Rust now 3 mentions
- Rewriting Bun in Rust 3 mentions
Also written as bun. Data: bun.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 45
“The toolchains it uses, Bun & Zig, do work there”
“At $work we've been refreshing the Bun release page for days, wondering when they would push the fix.”
“Bun also keeps improving at fast pace and constantly reduce memory usage which can be useful on budget server.”
“Both Bun and Node.js will execute Typescript directly without a compile step.”
“Bun also had far better compatibility with many libraries & native dependencies”
“It uses Bun a lot of the times.”
“I use bun for the sole reason of it running perfectly on riscv64”
“Stackwise we selected Three.js, typescript and bun”
“since I rely on Bun”
“that was when I started liking Bun so much”
“I use it heavily for personal use and find it works very well and lets me ship small applications quickly.”
“Bun is still massive”
“Bun seems very interesting since it allows you to do so many things without pulling in 3rd party libraries and bundlers?”
“Bun has been nothing but amazing wins for me”
“I use it daily and I've seen basically zero regressions.”
“I use the non-JS ones (esbuild, parcel, bun, etc.) and they're fast enough for me to not care.”
“It uses less memory in a Hono app compared to Node.js and Bun.”
“Bun being the canonical example of the sort of dumpster fire that comes from trying to hop from one language to the next”
“Claude Code uses the released bun runtime based on that code”
“Nobody is actually running it in production as a runtime. Why? Memory leaks and a whole bunch of other issues.”
“Building MPAs on Bun using Preact as the backend templating engine”
“I'm not going to trust my projects to a runtime that was written by an LLM in two weeks with practically no human review”
“I have a long running side project I migrated to bun, and I'm starting to regret it. I don't want to build on top of this much churn.”
“I love bun”
“Bun's rewrite has made me nervous about using it.”
“My take is they vibe coded too close to the sun”
“Bun would never have happened without Zig.”
“Until this bug is fixed, there's no trusting Bun”
“I use Bun as a Node.js replacement that works really well.”
“using Bun as the transpiler+bundler since it's so turnkey, and I ran into a few segfaults”
“the state of the code was very, very bad. There were 13,000 instances of `unsafe`”
“it has drastically reduced Bun's appeal”
“while doing a responsible migration (looking at you, Bun)”
“do it really faster than vite”
“why would I use this over bun?”
“It's just the discrepancy between not needing the newer version of vite/node on bun while invoking an error using deno.”
“it's not full-on vibe-developed like Deno and Bun”
“Bun is becoming a strong node replacement candidate”
“May integrate move from Bun to using Deno here”
“tons of issues appeared. Use-after-free bugs when a client disconnects”
“Can the same be said of Bun, which switched to an entirely different language in a single, million-line PR?”
“i would never ship a service at work on bun”
“I love coding with bun. It comes with everything.”
“I've been very satisfied since I switched to Bun. It's fast and has a great standard library.”
“Bun feels focused on meeting me where I am.”