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, 5:58:53 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

25 sources
Absolutely, but if I had to rank Open Source projects by "enjoyment level to work on", I would rank a 10+ year old Java project primarily used by enterprise companies quite low on my list! Compare that to something like Bun.js[0] which is "sexy" and written in a "cool" programming language (Zig). Or Wasp[1] which is built with Haskell and is trying to define a new programming language designed to make common dev patterns less painful. Those projects are naturally going to soak up smart people that have extra energy to share because they hate their day job but need to pay their bills. (imo) Who is left that wants to bang their head against a legacy codebase like Log4j? Maybe somebody that feels there is "clout" to be had from it? (Spitballing here, I honestly don't know!) 0: https://github.com/oven-sh/bun 1: https://github.com/wasp-lang/wa
Read the rest
In Log4Shell Still Has Sting in the Tail
Cool! Actually, cool is an understatement, but I'm too foreign to Imba to provide feedback on that front. Pretty sure there is enough to spark a discussion, but few bullet points: * Imba focused, yet you're greeted by TS example and the Imba demo is too dense to parse quickly * Not enough short info and too much text to spark my interest for reading * I still want to read something, so I head to GH repo (I have to search for actual core repo, plus I'm greeted by wall of text again) and when I found it, the README is bare :( https://github.com/oven-sh/bun and bun.sh are pleasant reads for me. All of this is subjective and might turn be a turn-off for hardcore folks, but that's not really the target audience for Imba anyway :) And don't fear the direct URL!
In Show HN: Yet Another Node.js Framework
I don't buy this argument. WebAssembly is a vastly different beast than trivial C extensions (since WASM is a browser thing). JavaScript has both and is still much faster. Bun (the runtime I used for the post), has a native C interface that's far simpler to use than Python (even with pybind/nanobind): https://github.com/oven-sh/bun#bunffi-foreign-functions-inte... Deno (a v8-based runtime) has the same thing: https://deno.land/manual@v1.25.4/runtime/ffi_api These use the standard C-ABI directly without requiring headers (unlike Python). Node.js standardized a more Python-like C API called Node-API: https://nodejs.org/api/n-api.html I believe Python can continue to add performance and is not hamstrung by the implementation.
In Python 3.11 is faster than 3.8
The version of that graph in the readme links to `bun/bench/react-hello-world` [0] which makes use of `react-dom/server` so it is a slightly more involved test than sending plain `hello world` On a local 4 core VM, generating the load locally: Deno.serve() appears to be particularly bad for me at this test until you crank up the concurrent connections (>500) it gets up to 2k rps but it also falls over after that load. The `react-hello-world.node.js` server in node peaks at about 1.5k rps @ 32 connection Bun running react-hello-world.jsx gets 8k rps with 32 connections. This uses a customised local copy of `react-dom/server` where [1] at least the `escapeHTML` function is switched for bun's native implementation, and this appears to be packaged (or will be?) with bun [2]. I'm not sure if anything else is different here as the bun packaged
Read the rest
code is still minified. The `bench/snippets/react-dom-render.bun.js` [3] test comparing these only show the bun version of `react-dom/server` to be 1.5 - 2x faster on this VM so it appears there is something more to it. Maybe everything `react-dom/server` normally stresses is optimised in bun? or `escapeHTML` is very large on the flamegraph. Running the react-hello-world.node.js server in bun results in about 1.9k rps @ 32 connection Running react-hello-world.deno.jsx in bun doesn't work. Futzing with react-hello-world.deno.jsx to load the cjs react builds will run in bun at about 1.9k rps 0: https://github.com/oven-sh/bun/tree/bun-v0.2.0/bench/react-h... 1: https://github.com/oven-sh/bun/blob/bun-v0.2.0/test/bun.js/r... 2: https://github.com/oven-sh/bun/blob/bun-v0.2.0/bench/react-h... 3: https://github.com/oven-sh/bun/blob/bun-v0.2.0/bench/snippet...
In Bun v0.2.0
Creator of Bun here. Regarding the SQLite claim: The "view source" link for SQLite is out of date (fixing shortly), but the numbers are correct. I forgot to change the label on the landing page from "x/sqlite" to "x/sqlite3" and I forgot to update the source link. You can see I updated in this git commit: https://github.com/oven-sh/bun/commit/4b5c9acc72908ba22e3f70... Here is what it shows for me, but I encourage you to run it on your own computer to see for yourself: deno run --unstable -A deno.js cpu: Apple M1 Max runtime: deno 1.26.1 (aarch64-apple-darwin) benchmark time (avg) (min … max) p75 p99 p995 ------------------------------------------------------------------- ----------------------------- SELECT \* FROM "Order" 26.3 ms/iter (25.06 ms … 29.2
Read the rest
3 ms) 26.74 ms 29.23 ms 29.23 ms SELECT \* FROM "Product" 53.91 µs/iter (52.17 µs … 317.75 µs) 54 µs 65.63 µs 76.75 µs SELECT \* FROM "OrderDetail" 269.41 ms/iter (240.72 ms … 308.82 ms) 279.05 ms 308.82 ms 308.82 ms bun bun.js [0.26ms] ".env" cpu: Apple M1 Max runtime: bun 0.2.0 (arm64-darwin) benchmark time (avg) (min … max) p75 p99 p995 ------------------------------------------------------------------- ----------------------------- SELECT \* FROM "Order" 14.44 ms/iter (13.71 ms … 17.82 ms) 14.56 ms 17.82 ms 17.82 ms SELECT \* FROM "Product" 34.39 µs/iter (30.46 µs … 4.55 ms) 32.88 µs 48.5 µs 60.13 µs SELECT \* FROM "OrderDetail" 148.17 ms/iter (144.8 ms … 154.92 ms) 149.85 ms 154.92 ms 154.92 ms Regarding the FFI benchmark, you can see the commit from today here: https://github.com/oven-sh/bun/commit/40506e33e73018103bcf08... It threw an error until I googled "Deno pointer ffi", which mentioned this function https://doc.deno.land/deno/unstable/~/Deno.UnsafePointer and that worked. I assumed that `Deno.UnsafePointer.of` is the expected way to get a pointer to a buffer, but it seems that changing the type to "buffer" is a faster way for this case. Will update the page shortly.
In Beware of Bun.js

Showing the 15 most recent of 25 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.