Bun's Roadmap

The Bun team updates this issue to share our current roadmap, priorities, and goals. You can see our current update below, and previous updates at the bottom.

Spring 2025

Node.js compatibility

For every change we make to Bun, we run the Node.js test suite to ensure that Bun is compatible with Node.js. We also started a bounty program within our team, to accelerate our progress.

Our goal is to be 90% compatible with Node.js. We'll be providing updates as our progress nears completion.

Features

While we continue to work on Node.js compatibility and bug fixes, we’re also going to be working on new features in upcoming releases of Bun, including:

• [x] #18812 Redis client
• [ ] #19699 MySQL support with Bun.sql
• [ ] #19701 SQLite support with Bun.sql (in addition to the existing bun:sqlite API)
• [ ] #4824 Test runner support in VSCode
• [ ] #7589 Running scripts with filters, and in parallel, using bun run
• [ ] #947 REPL support (replacement for existing, 3rd-party package: bun repl)
• [ ] Improve usage of bun install at work, including:
  • [ ] #7157 Support migration from pnpm-lock.yaml to bun.lock
  • [x] #4844 Support catalogs
  • [ ] #6608 Support nested resolutions and overrides
  • [ ] Fix issues with workspaces, private registries, and corporate proxies

Reliability

We're also hard at work improving Bun's reliability, for example, reducing crashes and memory leaks. We've been working on a few projects to help with this.

• [x] #19057 Address sanitizer (aka. ASAN)

  We now run address sanitizer in our CI, to detect bugs like heap buffer overflows

• [x] v1.2.2 10-30% less memory usage when idle

  We made changes to how Bun schedules garbage collection, so that it syncs with JavaScriptCore. This improves memory usage when Bun is idle.

• [ ] Distribute a debug/assertion build of Bun

  Sometimes it's difficult to reproduce crashes without having access to your source code. We will soon distribute a special, optional build of Bun that includes more assertions and debug logs, so that it's easier for you to provide us with reproductions of issues.

Hiring

Bun’s team is growing!

• 3 years ago, it was just Jarred.
• 2 years ago, we raised a Seed round and grew to a team of 4.
• Today, we're 14 people

We’re also announcing new job openings at our San Francisco office, including:

• Head of Propaganda (aka. Developer Advocate) for $120k-$180k + Equity
• Engineering Manager for $180k-$240k + Equity
• Senior Systems Engineer(s) for $160k-$220k + Equity

If you’re excited about working at Bun, you can apply at bun.sh/careers.

Something new

Stay tuned.

Previous updates

Winter 2024

bun install

• [x] https://github.com/oven-sh/bun/issues/11863 (will unblock https://github.com/dependabot/dependabot-core/issues/6528)
• [ ] https://github.com/oven-sh/bun/issues/6608
• [ ] Fixes for frequently-reported issues for things like private git URLs and some edgecases with hoisting
• [ ] bun update --interactive (https://github.com/oven-sh/bun/issues/4895)
• [x] https://github.com/oven-sh/bun/issues/271
• [ ] https://github.com/oven-sh/bun/issues/5846
• [ ] Update bun init to add "engines": { "bun": ... by default. If bun present then ignore node shebangs by default (#9346)
• [ ] https://github.com/oven-sh/bun/issues/692

Runtime

Node.js compatibility

• [x] Implement node:http2 server to unblock grpc2
• [ ] Implement more of V8 C++ APIs to unblock canvas, node-pty
• [ ] Rewrite node:http (https://github.com/oven-sh/bun/pull/14384)
• [ ] Add much more comprehensive test coverage for napi
• [ ] Get at least 75% of Node's test suite running on every commit (as of last update: 37% currently). This number will go up in future
• [ ] Investigate removing our undici override
• [x] https://github.com/oven-sh/bun/issues/13681
• [ ] https://github.com/oven-sh/bun/issues/1723

Reliability

• [ ] https://github.com/oven-sh/bun/issues/15141

Bake (Bundler)

The goal for Bake is to make Bun the most productive tool for building static & full-stack JavaScript and TypeScript applications, leveraging runtime, bundler, and transpiler integration to make things simpler.

High level:

• [ ] Make a fast HMR development full-stack server - https://github.com/oven-sh/bun/issues/14324
• [ ] Production builds (#14763)
  • [x] Static production builds
• [ ] Implement an integration with a popular framework (such as Next.js)
• [ ] Easy & powerful plugin API

bun test

• [x] Reporter API or socket API

Organizational

• [x] Hire a contractor to help us with CI
• [ ] Hire a technical writer to help with docs
• [ ] Hire an engineering-focused role for maintaining the TypeScript types & frontend for docs + help with integrations with third-party packages
• [ ] Hire more systems engineers

Fall 2024

bun install

Essentially, feature complete.

• [x] bun outdated
• [x] https://github.com/oven-sh/bun/issues/487
• [x] bun publish
• [ ] Text-based lockfile format (which will help unblock https://github.com/dependabot/dependabot-core/issues/6528)
• [ ] bun update --interactive (https://github.com/oven-sh/bun/issues/4895)
• [ ] Fixes for frequently-reported issues for things like private git URLs and some edgecases with hoisting

Runtime

Node.js compatibility

• [x] TextEncoderStream & TextDecoderStream
• [x] V8 C++ API (in-progress)
• [x] Implement node:cluster
• [ ] Implement node:http2 server to unblock grpc2
• [x] Rewrite node:zlib to address performance issues in some common packages
• [x] https://github.com/oven-sh/bun/issues/13681
• [ ] Fix various bugs in node:http, avoid wrapping Bun.serve() and fetch() and use a more direct implementation
• [ ] Add much more comprehensive test coverage for napi
• [ ] Get at least 25% of Node's test suite running on every commit (as of last update: 15% currently). This number will go up in future quarters.

Reliability

• [ ] Delete almost all code that manually reads JSValue. Replace with an IDL bindings generator for JavaScriptCore objects/classes that supports C++ & Zig output, and importantly: function arguments, return values, and exceptions. It should make the lifetime of these values brainless for us to reason about.
• [x] Address TLS-related issues that have cropped up
• [x] Continue to allocate significant time to fixing bugs and improve test coverage as they crop up

Bundler

• [x] Fix many common bugs people run into related to source maps or incorrect output
• [ ] A new, higher-level iteration of Bun's bundler designed for server-driven JavaScript #14324
• [x] CSS parser and bundler #14167

bun test

• [ ] Reporter API or socket API

Organizational

• [ ] Hire a contractor to help us with CI
• [ ] Hire a technical writer to help with docs
• [ ] Hire an engineering-focused role for maintaining the TypeScript types & frontend for docs + help with integrations with third-party packages
• [ ] Hire more systems engineers

this seems like a lot of work... wow

Can't wait for full npm-like config support. We are using our own npm registry, and the current build time is 40-60 minutes. If it will be at least 10 minutes this will be a game-changer!

I am waiting for the stable version of the bun. What change bun in the javascript world.

Also waiting for the stable version. So exciting! I bet it's going to take a lot of time though. The scope of this project is much larger than what Node attempts to solve.

can someone confirm that right now I can't use the package mysql2? It throws me an error because it depends on TLS package and on NET package, and I think they were not implemented yet in Bun, but I am not sure.

still missing websocket server support

Can a tinitiny docker image be placed somewhere in there? 👀

Can't wait for Windows support... I'll be anxiously awaiting it until it's out. 😅

still missing websocket server support

Dito

Are you planning to support http2?

Are you planning to support http2?

HTTP/3 is on https://github.com/oven-sh/bun/issues/159 so I would say HTTP/2 will likely be added before that

Are you planning to support http2?

HTTP/3 is on #159 so I would say HTTP/2 will likely be added before that

I would say that http3 on roadmap is more about quic protocol and there is no straight inheritance between http3 and http2, so maybe support of http2 needs to be marked explicitly.

Motivated to see a stable version ASAP

Promising ! Any roadmap on a progressive translation ?

When is the support for windows coming? Cant wait for it.

I would say that http3 on roadmap is more about quic protocol and there is no straight inheritance between http3 and http2, so maybe support of http2 needs to be marked explicitly.

Another vote for HTTP/2 as it's a prerequisite to gRPC support.

Any plans to create a desktop app like electron?

When is the support for windows coming? Cant wait for it.

https://github.com/oven-sh/bun/issues/43 you can use WSL for now

When is the support for windows coming? Cant wait for it.

#43 you can use WSL for now

I don't use WSL. Node.js and Deno support Windows natively; why can't Bun?

When is the support for windows coming? Cant wait for it.

#43 you can use WSL for now

I don't use WSL. Node.js and Deno support Windows natively; why can't Bun?

Check https://github.com/oven-sh/bun/issues/43

On the topic of CSS parsing, transpilation, minification, etc., what's your stance on dependencies? Do you want to reimplement everything yourself, or would you consider using an embeddable library? If so, I'd love to collaborate with you on embedding Parcel CSS in Bun. It's implemented in Rust, but if we added a C API, I think Bun could call into it pretty easily. It may also work via Bun's napi support, but that would probably be slower. It's about 4x faster than esbuild on benchmarks, minifying over 2 million lines of code per second on a single thread. You can find more info in the announcement blog post from February, though it's gotten even faster since then. Would be cool to work together, and I'm happy to help support how I can.

One thought re: minification, please include a way to exclude class/parameter (on both function and constructor args, and incl. subkeys)/function names from minification as it makes certain dependency injection patterns impossible.

Traditionally, many of the existing DI libraries would use Function.toString() and then use some regex to pull out the fn name & args, but given the reason that is needed and how hacky it is, this may be an opportunity for bun to create a better solution ahead of time, for example by exposing the pre-minified function/class names + argument names programmatically such that they are available at runtime. Note that they much be able to be retrieved before the function is called or class is instantiated.

How about full support for NestJS? Looking forward to it.

[ ] read resolutions from package.json

Bun should move toward full support for nestjs.

Are there any plans for bun language server? Deno provides one: https://deno.land/[email protected]/advanced/language_server/overview, so I thought bun might do as well

Bun === GOAT

Setup a donations button!!

As an Electron or Tauri alternative. Maybe should consider to build single-file executable files. .exe or .msi for windows and .dmg and .pkg for macos.

Would love to eventually see support for Qwik. Down the line would be willing to help with the effort too.

Would love to eventually see support for Qwik. Down the line would be willing to help with the effort too.

Yes!!!!!!!!!!!!!!!!! Qwik + Bun === GOAT