Skip to content

Bun's Roadmap #159

Open
Open
Bun's Roadmap#159
Labels
trackingAn umbrella issue for tracking big features

Description

@Jarred-Sumner
Jarred-Sumner
opened on May 6, 2022

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.

Image

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:

  • #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
    • #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.

  • #19057 Address sanitizer (aka. ASAN)

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

  • 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:

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

Something new

Stay tuned.

Image

Previous updates

Winter 2024

bun install

Runtime

Node.js compatibility

Reliability

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:

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
Fall 2024

bun install

Essentially, feature complete.

Runtime

Node.js compatibility

  • TextEncoderStream & TextDecoderStream
  • V8 C++ API (in-progress)
  • Implement node:cluster
  • Implement node:http2 server to unblock grpc2
  • Rewrite node:zlib to address performance issues in some common packages
  • Rewrite node:crypto #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.
  • Address TLS-related issues that have cropped up
  • Continue to allocate significant time to fixing bugs and improve test coverage as they crop up

Bundler

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

Activity

  1. Jarred-Sumner
    pinned this issue on Jul 2, 2022

  2. RnbWd commented on Jul 7, 2022

    @RnbWd
    RnbWd
    on Jul 7, 2022

    this seems like a lot of work... wow

  3. FinnRG
    added
    trackingAn umbrella issue for tracking big features
    on Jul 9, 2022

  4. space7panda commented on Jul 11, 2022

    @space7panda
    space7panda
    on Jul 11, 2022

    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!

  5. officialrajdeepsingh commented on Jul 11, 2022

    @officialrajdeepsingh
    officialrajdeepsingh
    on Jul 11, 2022

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

  6. tipiirai commented on Jul 12, 2022

    @tipiirai
    tipiirai
    on Jul 12, 2022

    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.

  7. matepaiva commented on Jul 12, 2022

    @matepaiva
    matepaiva
    on Jul 12, 2022

    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.

  8. Kapsonfire commented on Jul 12, 2022

    @Kapsonfire
    Kapsonfire
    on Jul 12, 2022
    Contributor

    still missing websocket server support

  9. GCSBOSS commented on Jul 12, 2022

    @GCSBOSS
    GCSBOSS
    on Jul 12, 2022

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

  10. MystPi commented on Jul 14, 2022

    @MystPi
    MystPi
    on Jul 14, 2022

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

  11. 0x4a61636f62 commented on Jul 17, 2022

    @0x4a61636f62
    0x4a61636f62
    on Jul 17, 2022

    still missing websocket server support

    Dito

  12. sodeprecated commented on Jul 17, 2022

    @sodeprecated
    sodeprecated
    on Jul 17, 2022

    Are you planning to support http2?

  13. moderation commented on Jul 18, 2022

    @moderation
    moderation
    on Jul 18, 2022

    Are you planning to support http2?

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

  14. sodeprecated commented on Jul 18, 2022

    @sodeprecated
    sodeprecated
    on Jul 18, 2022

    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.

  15. frodoe7 commented on Jul 19, 2022

    @frodoe7
    frodoe7
    on Jul 19, 2022

    Motivated to see a stable version ASAP

  16. 160 remaining items

  17. libersoft-org commented on Oct 26, 2025

    @libersoft-org
    libersoft-org
    on Oct 26, 2025

    Spring 2025 is over for many months now. Can you update the roadmap, please?

  18. digitalextremist commented on Oct 26, 2025

    @digitalextremist
    digitalextremist
    on Oct 26, 2025

    Technically it is Spring 2025 in the Southern Hemisphere right now, but yes 😆 @libersoft-org

  19. libersoft-org commented on Nov 7, 2025

    @libersoft-org
    libersoft-org
    on Nov 7, 2025

    Still no update? Bun devs, where are you?

  20. marziply commented on Nov 7, 2025

    @marziply
    marziply
    on Nov 7, 2025

    what-huh.gif

  21. onur-zenotech commented on Nov 26, 2025

    @onur-zenotech
    onur-zenotech
    on Nov 26, 2025

    I think we need ts-zig instead of ts-go :D I'm sure that this team can develop Typescript 7 (aka: ts-go) faster and better than Microsoft. The only remaining big problem affects every TS developer is slow language server nowadays. Deno wrote one (buggy and not compatible with original TS) why cant Bun team write one.

  22. IshmamR commented on Dec 26, 2025

    @IshmamR
    IshmamR
    on Dec 26, 2025

    Bun should probably focus on open issues as it now has a stable income source.
    There are like 60+ issues just on memory leaks and it's making bun a bad competitor as a server runtime on production grade software.

  23. libersoft-org commented on Dec 26, 2025

    @libersoft-org
    libersoft-org
    on Dec 26, 2025

    Bun should probably focus on open issues as it now has a stable income source. There are like 60+ issues just on memory leaks and it's making bun a bad competitor as a server runtime on production grade software.

    And most requested new features too :) I would gladly help them financially if they start communicating with us, but I wrote them e-mails many times and never got replied back. Wonderful project, horrible customer / tech. support.

  24. digitalextremist commented on Dec 26, 2025

    @digitalextremist
    digitalextremist
    on Dec 26, 2025

    I have only seen excellent support, and amazing professionalism. I do not see the logic of these last two posts at all.

    Right now, Bun is gifted to the Open Source space. We have no significant value to Bun / Anthropic unless we contribute first and ask questions later. To matter, we need to match / surpass their performance ( which already sets the bar in the field right now ) ... otherwise we are just being a burden, and it would be wise to just ignore the community versus cultivate it further. We need to focus on doing awesome work that raises the bar, and motivate with value.

    Right now Bun has all the best qualities in one of the most rapidly growing world-dominating language ecosystems... it is doing its job better than anyone else. What about us? We cannot freeride our way forward and complain and whip-crack. We need to provide more value than we consume here, and inspire them to do more. In my experience, they always rise to that occasion. This is one of the most valuable areas of Open Source in all of history. It is awesomeness driven.

    Please do not kill the vibe during that historic success, and get really motivated to overcome whatever holds us back, which is not Bun but our own work. It would be appreciated if we can be cool and let awesome do what awesome wants.

  25. VillainsRule commented on Dec 26, 2025

    @VillainsRule
    VillainsRule
    on Dec 26, 2025

    Bun is FOSS software. No one here has denied that. Nonetheless, Bun still has thousands of issues. I've opened issues on this repository with them overtime, and some have been fixed, while some have not. No one here is "complaining".

  26. eveeifyeve commented on Dec 26, 2025

    @eveeifyeve
    eveeifyeve
    on Dec 26, 2025

    Can someone on the bun team please lock this issue or something if some people need an issue added they can link back to this issue with their own created issue?

    It's very annoying to have 1000+ pings from here from random people that want their issue fixed but they haven't touched a single part of bun code in zig. At the end of the day I have this subbed so I can see updates on the quarterly updates and it's getting annoying.

    NOTE: If you want it fixed and prioritized then fix it yourself else create an issue and wait patiently for them to prioritize your issue.

  27. AccessNull commented on Jan 2, 2026

    @AccessNull
    AccessNull
    on Jan 2, 2026 · Hidden as spam

  28. ClementValot commented on Jan 2, 2026

    @ClementValot
    ClementValot
    on Jan 2, 2026 · Hidden as off-topic

  29. VillainsRule commented on Jan 2, 2026

    @VillainsRule
    VillainsRule
    on Jan 2, 2026 · Hidden as spam
  30. oven-sh
    locked and limited conversation to collaborators on Jan 2, 2026
  31. alii
    unpinned this issue on Apr 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    trackingAn umbrella issue for tracking big features

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions