Bun's Roadmap

[Jarred-Sumner]

Bun's roadmap

2024 Q4

bun install

• Implement a text-based lockfile format #11863 (will unblock add support for bun dependabot/dependabot-core#6528)
• Support nested "resolutions" / "overrides" #6608
• Fixes for frequently-reported issues for things like private git URLs and some edgecases with hoisting
• bun update --interactive (Interactive update packages command. #4895)
• CA support for SSL connection to NPM registries #271
• Support an "engines" field in package.json #5846
• Update bun init to add "engines": { "bun": ... by default. If bun present then ignore node shebangs by default (#9346)
• bun why (like yarn why) #692

Runtime

Node.js compatibility

• Implement node:http2 server to unblock grpc2
• Implement more of V8 C++ APIs to unblock canvas, node-pty
• Rewrite node:http (Rewrite node:http to not use Request & Response #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: 15% currently). This number will go up in future
• Investigate removing our undici override
• Rewrite node:crypto #13681

Reliability

• tracking: JSValue safety in our Zig and JS bindings #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 - bake dev server tracking issue #14324
• Production builds (bake production build tracking issue #14763)
  • Static production builds
• Implement an integration with a popular framework (such as Next.js)
• Easy & powerful plugin API

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

Previous quarters

2024 Q3

bun install

Essentially, feature complete.

• bun outdated
• Implement bun pm pack #487
• bun publish
• Text-based lockfile format (which will help unblock add support for bun dependabot/dependabot-core#6528)
• bun update --interactive (Interactive update packages command. #4895)
• Fixes for frequently-reported issues for things like private git URLs and some edgecases with hoisting

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

• 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 bake dev server tracking issue #14324
• CSS parser and bundler MVP of CSS parser #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

[RnbWd]

this seems like a lot of work... wow

[space7panda]

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!

[officialrajdeepsingh]

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

[tipiirai]

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.

[matepaiva]

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.

[Kapsonfire-DE]

still missing websocket server support

[GCSBOSS]

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

[MystPi]

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

[0x4a61636f62]

still missing websocket server support

Dito

[sodeprecated]

Are you planning to support http2?

[moderation]

Are you planning to support http2?

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

[sodeprecated]

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.

[frodoe7]

Motivated to see a stable version ASAP

[LaurelineP]

Promising !
Any roadmap on a progressive translation ?

[Parvat-R]

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

[jacoscaz]

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.

[dyaskur]

Any plans to create a desktop app like electron?

[xhyrom]

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

#43 you can use WSL for now

[eknowles]

@Jarred-Sumner i think many more of these items can now be ticked off 🙌

[jhaemin]

I'm still waiting for IIFE output format. It's the only reason I can't use Bun as a bundler.

[Jarred-Sumner]

Updated.

[libersoft-org]

Any plans for HTTP/3 and WebTransport?

Thank you.

[tomaszzmudzinski]

Any plans to change this?

"The Next.js App Router currently relies on Node.js APIs that Bun does not yet implement. The guide below uses Bun to initialize a project and install dependencies, but it uses Node.js to run the dev server."

[Gadrawingz]

I am balancing Node.js + Fastify vs Bun + Hono

[danielniccoli]

@Jarred-Sumner Why have you removed the Streams APIs from the roadmap? Are these tracked elsewhere? Or have these be removed entirely from the roadmap?

[Eveeifyeve]

Sorry I mentioned it cause I like the idea of bun roadmap I thought I will credit it.

[Movsar-Khalakhoev]

Easy & powerful plugin API

Is there an example of what the plugin API interface will look like? Would like to see the possibility of transforming the code using the visitor pattern, as it is done in @babel/traverse

[kravetsone]

Why not bun update -i not by default?
I guess it would be more convinient

[Eveeifyeve]

Why not bun update -i not by default? I guess it would be more convinient

--interactive can be short alaised to -i I am looking to do this but I need some help from @Jarred-Sumner or someone to get to me a basic idea what it will look like and etc.
#4895 (comment)

[kravetsone]

Why not bun update -i not by default? I guess it would be more convinient

--interactive can be short alaised to -i I am looking to do this but I need some help from @Jarred-Sumner or someone to get to me a basic idea what it will look like and etc.
#4895 (comment)

I mean interactive by default not in CI without flagging

[Eveeifyeve]

Why not bun update -i not by default? I guess it would be more convinient

--interactive can be short alaised to -i I am looking to do this but I need some help from @Jarred-Sumner or someone to get to me a basic idea what it will look like and etc.
#4895 (comment)

I mean interactive by default not in CI without flagging

Not really because interactive should be optional that’s how pnpm and yarn do it is where they update everything and if you need interactive then you use the flag.

[kravetsone]

Why not bun update -i not by default? I guess it would be more convinient

--interactive can be short alaised to -i I am looking to do this but I need some help from @Jarred-Sumner or someone to get to me a basic idea what it will look like and etc.
#4895 (comment)

I mean interactive by default not in CI without flagging

Not really because interactive should be optional that’s how pnpm and yarn do it is where they update everything and if you need interactive then you use the flag.

but what usecase to not use interactivity? i guess it more better to know what u bumps

also just add --all flag to bump all deps without interactivity

[Eveeifyeve]

Why not bun update -i not by default? I guess it would be more convinient

--interactive can be short alaised to -i I am looking to do this but I need some help from @Jarred-Sumner or someone to get to me a basic idea what it will look like and etc.
#4895 (comment)

I mean interactive by default not in CI without flagging

Not really because interactive should be optional that’s how pnpm and yarn do it is where they update everything and if you need interactive then you use the flag.

but what usecase to not use interactivity? i guess it more better to know what u bumps

also just add --all flag to bump all deps without interactivity

Because interactively is bearly used and will be a pain in way when you just trying to update all deps. By default it should be updates all deps but you have the option to interactively update deps using -i or --interactive

[danielniccoli]

@kravetsone It is idiomatic in Linux and Windows that shell commands should be non-interactive first if they are meant to be used in both ways. And for bun this is certainly the case.

@Eveeifyeve While it is good to have your opinion formed by outside factors, I'd certainly say that there are better arguments than looking at yarn or pnpm to decide what bun should do (see my above argument). Whether or not interactive is bearly used needs some sources and whether it is a pain is certainly subjective. :)

I would recommend to move that discussion into the Discussions section. Saying that, commenting on the matter makes me guilty as well :)

[Eveeifyeve]

@Eveeifyeve While it is good to have your opinion formed by outside factors, I'd certainly say that there are better arguments than looking at > yarn or pnpm to decide what bun should do (see my above argument).

I will look at your above argument.

Whether or not interactive is bearly used needs some sources and > whether it is a pain is certainly subjective. :)

I can't find some sources, but I know there is some data out there.

I would recommend to move that discussion into the Discussions section. Saying that, commenting on the matter makes me guilty as well :)

Or the bun discord using the threads thing.

[RobinKnipe]

Why not bun update -i not by default? I guess it would be more convinient

If you want to change the way a command works for you, why not just create an alias? e.g.

# in ~/.bash_aliases
alias buni='bun update -i'

[Eveeifyeve]

@danielniccoli You ever get an answer on your streams inquiry? You are talking about WHATWG Streams, correct?

Um This is not related idk why you even mentioned this.

@Jarred-Sumner @paperdave.

[Eveeifyeve]

Um This is not related idk why you even mentioned this.

@Eveeifyeve

Clearly for clarification.

WHATWG Streams are what's going on circa 2024, not necessarily Node.js-specific "node:stream".

Just report it if it's an issue if it's a discussion please take it to discussions on GitHub (which I don't know is enabled) or bun discord.