HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
oven-sh
bun
Rust2022–2026
oven-sh / bun

bun

Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one

204Distinct people
267Mentions
2Explicit recommenders
96.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one

GitHub

Where it is used

  • Netlify Builds — Netlify Builds exposes the Bun executable during builds so developers can run their build commands with the Bun runtime. This provides out-of-the-box Bun support in the build environment. Source
  • Vercel Functions — Vercel Functions uses Bun as a runtime option to run functions. Teams can choose Bun instead of Node.js for their projects. Source

What people are saying

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…

weli used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM UTC.

Mentions over time

HN mentions by year267 dated mentions

Observed mentions: 2022-07-12 10:17:18 UTC to 2026-10-24 19:16:24 UTC.

0501001502022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 25 mentions; 6 submissions, 19 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 37 mentions; 0 submissions, 37 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 25 mentions; 1 submissions, 24 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 43 mentions; 3 submissions, 40 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 137 mentions; 29 submissions, 108 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC25619
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC37037
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC25124
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC43340
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC13729108

What Hacker News says

37 sources
TL;DR: It is too buggy. I tried it and ran into many issues. For example: - Incompatibility of transpiled artifacts with the Node runtime (many bugs were fixed, but I haven't tried again). I don't trust bun as a runtime. - Broken monorepo support. - No direct react support; you still need react-scripts/webpack/whatever. They have documentation on transpiling react, but it isn't the same. - No type checking, as with many other tools. Also, filter their issue tracker for bugs: https://github.com/oven-sh/bun/issues?q=is%3Aissue+is%3Aopen...
In A Node, TypeScript, TS-Node and ESM experience that works
One of Bun's assertions is that their AsyncLocalStorage is significantly faster than Node's, b/c it purposefully only implements the subset of async_hooks that can be implemented w/o affecting performance: https://github.com/oven-sh/bun/pull/3089 I haven't had a chance to test it out yet, but perhaps the OP could add Bun to the mix? To compare it's promise overhead vs. Node's promise overhead. Also there is an issue in Node about performing the same optimization: https://github.com/nodejs/node/issues/46265
In The Performance Cost of Node.js and GraphQL
I hear you! I went all-in to jQuery- scene. Even wrote a semi-famous library called "jQuery Tools" (oldies know). Then came React and I wrote Riot to simplify the syntax. Then I sidetracked to a startup world for (too) many years and watched aside how the frontend ecosystem grew to it's current dimensions. Node uses a single dependency, htmlparser2 [1], in the package.json [2]. The HTML parser is used to traverse the HTML that is written on the Nue files. I quickly _thought_ of writing my own parser, but right now I'm having my eyes staring at Bun's native HTML parsing capabilities. Instead of Node, I'm using Bun to develop everything. I need less dependencies with it, because things like JS minification or .env file parsing are biult in. Avoiding NPM dependencies is a high priority! [1]: https://github.com/fb55/htmlparser2 [2]: https://g
Read the rest
In Show HN: Nue – A React/Vue/Vite/Astro Alternative
Jarred congrats for the release! I've been following the progress of bun since your initial announcement and today I decided to give it a try, just to play around. Haven't done much with it, but even for the 5 min I played with it I'm kind of impressed so far. - Superquick install PLUS did not require root (like many other installs) - It identified I was using fish shell and added to path (nice!) - I ran a very quick bench on "npm install" vs "bun install" on one of the projects I have, and the performance is amazing. 50seconds vs 4.5 seconds on the first install. Moreover re-executing "bun install" takes 122ms on my machine. Removing node_modules and re-executing it takes 769ms (because of course, it uses a local cache elsewhere, but still). Amazing. I'll probably continue exploring tomorrow and see whether it is able to run the rest of
Read the rest
the backend/frontend or whether it gives me a hard time. I've seen there are certain things that are not 100% compatible with node yet, but since the initial impressions are great I'll explore further. BTW A code formatter and a linter would be a great addition to bun. I know there is this ticket: https://github.com/oven-sh/bun/discussions/712 But one of the advantages of integrating both things in bun is that it makes it the perfect standard tool to be used inside of a team. So no extra installations from other projects, no extra mental burden of what to use, etc... bun would be the perfect dev companion with both ;) Probably a linter is a different beast (and not sure you or the rest of people working in bun want to get in there... probably not important right now), but a formatter seems doable and it does add a lot of value from my point of view. Given that bun already runs, installs, tests and bundles, to the very least _formatting_ seems like a natural addition to the family. To me a formatter is part of the standard toolset for developers nowadays. Once again, thanks a lot for the effort to you and the rest of the people contributing to the project! (edit: re-formatted my comment :p)
In Bun v1.0.0
How does Bun support CJS and ESM in the same file? Is it transpiling CJS to ESM? Or is it transpiling ESM to CJS? ESM can use top-level await and CJS can't. So this can't possibly work, right? // x.mjs export const x = await 'x'; // y.cjs console.log(require('./x.mjs').x); And, indeed, it doesn't work in Bun. When I `bun y.cjs` it gives me this error message: TypeError: require() async module "/tmp/x.mjs" is unsupported. use "await import()" instead. … but using "await import()" instead is exactly what I was trying to avoid! I can use "await import()" in Node, too. But it looks like it does work in Bun if I drop the `await` from y.mjs. So, is it just transpiling ESM to CJS, and failing out if the ESM uses top-level await? EDIT: I see the documentation page https://bun.sh/docs/runtime/modules has a "low-level details"
Read the rest
section, explaining how import(CJS) works (by transpiling CJS to ESM), but it doesn't say anything there about how require(ESM) works, which is unfortunate, because that's by far the most interesting part! I've filed a doc bug on this. https://github.com/oven-sh/bun/issues/4601
In Bun v1.0.0
If Bun is able to run and bundle a TypeScript React app out-of-the-box, what are the benefits of using Vite.js on top of it? I'm confused cause this guide on the official site showcases how to use Bun + Vite.js to build a TypeScript React app. [1] There is also this issue on their Github. [2] Can Vite.js be used to handle more complicated scenarios / advanced use cases that Bun doesn't handle? My use of Vite.js is pretty basic (start & build with the default TS+React config) so maybe I'm missing something here. -- [1] https://bun.sh/guides/ecosystem/vite [2] https://github.com/oven-sh/bun/issues/250
In Bun v1.0.0

Showing the 15 most recent of 37 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.