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

25 sources
Bun | Software Engineer (systems, runtime, i/o) | Fulltime | Onsite in San Francisco | https://bun.sh Bun is an open-source JavaScript tooling company focused on making programming simpler. Today, Bun is a JavaScript runtime designed to be a faster drop-in replacement for Node.js, along with an incredibly fast npm client, jest-compatible test runner, and JavaScript transpiler, minifier, and bundler. We're hiring systems engineers to come to San Francisco and help us make JavaScript faster and more productive. This role will involve lots of open-source low-level systems work, mostly in Bun's GitHub repo - https://github.com/oven-sh/bun and also in a commercial hosting product. Apply here: https://apply.workable.com/oven/j/A7A1388873/ Most of our code is in Zig and C++ and open-source. To see what we do every day, have a look at the recent
Read the rest
pull requests.
In Ask HN: Who is hiring? (September 2024)
JSX can become valid, standardized ECMAScript syntax. But first we need a valid syntactic sugar transformation, which I propose here. Then we need to implement it in things like babel[0] bun[1] and deno[2]. Then, frameworks would adopt it as an optional alternative implementation. Eventually, it could gain widespread support and become standardized. [0] https://github.com/sdegutis/vanillajsx.com/blob/main/site/un... [1] https://github.com/oven-sh/bun/issues/13630 [2] https://github.com/denoland/deno/issues/25312
In Proposal for Standardized JSX
Bun is amazing, but I recently tried to make an http/2 server through fastify and was not able to: user@host:~/d/temp/server$ bun run index_fastify.js 14 | warned.add(feature), console.warn(new NotImplementedError(feature, issue)); 15 | }, $; 16 | 17 | class NotImplementedError extends Error { 18 | code; 19 | constructor(feature, issue) { ^ NotImplementedError: node:http2 createServer is not yet implemented in Bun. Track the status & thumbs up the issue: https://github.com/oven-sh/bun/issues/887 code: "ERR_NOT_IMPLEMENTED" at new NotImplementedError (internal:shared:19:27) at internal:shared:2:69 at node:http2:48:53 at getServerInstance (/Users/user/d/temp/server/node_modules/fastify/lib/server.js:342:16)
Read the rest
at createServer (/Users/user/d/temp/server/node_modules/fastify/lib/server.js:25:18) at fastify (/Users/user/d/temp/server/node_modules/fastify/fastify.js:198:30) at /Users/user/d/temp/server/index_fastify.js:4:13 The linked issue is actually about implementing support for http/2 clients, which was already released in v1.0.13 (https://bun.sh/blog/bun-v1.0.13#http2-client-support). The NotImplementedError message should be updated to point to the issue for the server variant: https://github.com/oven-sh/bun/issues/8823 Implementing http/2 server support is in the top few feature requests (https://github.com/oven-sh/bun/issues?q=is%3Aissue+is%3Aopen...). It looks like once they ship this, a lot more people will be able to move over to Bun.
In Bun’s New Crash Reporter
I found Bun to be faster. Monorepo support is a bit kludgy though. Once you know of the workarounds, it's ok. See my comment on https://github.com/oven-sh/bun/issues/5413#issuecomment-1956... AFAIK, Pnpm monorepos do not follow standard npm. Bun does follow standard npm monorepos. Pnpm's feature to override dependency versions is nice for legacy projects with many 3rd party dependencies. Not sure if Bun has the same feature. I mostly use it on greenfield projects with dependencies that I control.
In Bun 1.1
I was quite curious about the .bunx file format. I think this could be a quite a useful thing, a universal binary format. Then I see the shim DLL: https://github.com/oven-sh/bun/blob/801e475c72b3573a91e0fb4c... Even before this past week's XZ backdoor revelation, checking binaries into source control rather than building from source seems quite questionable. In fairness to the Bun developer's, they have a comment in their build.zig file acknowledging that this shim should be built more normally rather than being checked in. Then I look into the source for it: https://github.com/oven-sh/bun/blob/801e475c72b3573a91e0fb4c... For no discernible reason, it is using a bunch of undocumented Windows APIs. The source cites this Zig issue as one reason for why they think it is OK to use undocumented APIs: https://github.com/ziglang/zig/issues/1840
Read the rest
I don't see any good reasons here cited for using undocumented, unstable interfaces. For Zig's part, there seems to be some poorly-explained interest in linking against "lower level" libraries without any motivating use case (just some hand waving about security and drivers, neither of which makes much sense. Onecore.lib is a thing if you wanted a documented way of linking an executable that run on a diverse set of Windows form factors. And compiling drivers may as well be treated as a seperate target, since function names are different). For Bun, I assume they are trying to have low binary size. But targeting NTDLL vs. Kernel32 should not make a big difference, especially when the shim is just doing basic file IO. For an example of making small executable with standard API, you can make hello world 4kb using MSVC just by using /NODEFAULTLIB and /ENTRY:main with link.exe and this program : #include <Windows.h> #define MY_MSG "Hello World!\n" int main() { WriteFile(GetStdHandle(STD_OUTPUT_HANDLE), MY_MSG, sizeof(MY_MSG), nullptr, nullptr); return 0; } So it should be possible to make a .bunx shim of small size without having to resort to undocumented API. (Current exe is 12kb). But even if the shim exe was 100kb, that would be still be an acceptable tradeoff for me than having to debug any problem that results from using non-standard APIs.
In Bun 1.1
Kind of. When you do try to run bun in production you'll find out that it has significant differences to node -- like not handling uncaught exceptions: https://github.com/oven-sh/bun/issues/429 Then you'll use bun build and run node in production, only to find that sourcemaps don't actually work at all: https://github.com/oven-sh/bun/issues/7427 So you'll switch to esbuild + node in production :) Definitely excited for the promise of bun, but it's not quite baked yet.
In Bun 1.1

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.