Contributing

Configuring a development environment for Bun can take 10-30 minutes depending on your internet connection and computer speed. You will need ~10GB of free disk space for the repository and build artifacts. If you are using Windows, please refer to this guide

Using Nix (Alternative)

A Nix flake is provided as an alternative to manual dependency installation:

nix develop
# or explicitly use the pure shell
# nix develop .#pure
export CMAKE_SYSTEM_PROCESSOR=$(uname -m)
bun bd

This provides all dependencies in an isolated, reproducible environment without requiring sudo.

Install Dependencies (Manual)

Using your system’s package manager, install Bun’s dependencies:

brew install automake ccache cmake coreutils gnu-sed go icu4c libiconv libtool ninja pkg-config rustup-init ruby

sudo apt install curl wget lsb-release software-properties-common cmake git golang libtool ninja-build pkg-config ruby-full xz-utils

sudo pacman -S base-devel cmake git go libiconv libtool make ninja pkg-config python rustup sed unzip ruby

sudo dnf install clang21 llvm21 lld21 cmake git golang libtool ninja-build pkg-config ruby libatomic-static libstdc++-static sed unzip which libicu-devel 'perl(Math::BigInt)'

sudo zypper install go cmake ninja automake git icu rustup

Bun is written in Rust and requires a specific nightly toolchain (pinned in rust-toolchain.toml). Install Rust via rustup rather than your distro’s rust/cargo packages — the build scripts use rustup to automatically install and update the pinned nightly:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Before starting, you will need to already have a release build of Bun installed, as we use our bundler to transpile and minify our code, as well as for code generation scripts.

curl -fsSL https://bun.com/install | bash

npm install -g bun

brew tap oven-sh/bun
brew install bun

Optional: Install `ccache`

ccache is used to cache compilation artifacts, significantly speeding up builds:

# For macOS
brew install ccache

# For Ubuntu/Debian
sudo apt install ccache

# For Arch
sudo pacman -S ccache

# For Fedora
sudo dnf install ccache

# For openSUSE
sudo zypper install ccache

Our build scripts will automatically detect and use ccache if available. You can check cache statistics with ccache --show-stats.

Install LLVM

Bun requires LLVM 21.1.8 (clang is part of LLVM). This version is enforced by the build system — mismatching versions will cause memory allocation failures at runtime. In most cases, you can install LLVM through your system package manager:

brew install llvm@21

# LLVM has an automatic installation script that is compatible with all versions of Ubuntu
wget https://apt.llvm.org/llvm.sh -O - | sudo bash -s -- 21 all

sudo pacman -S llvm clang lld

sudo dnf install llvm clang lld-devel

sudo zypper install clang21 lld21 llvm21

If none of the above solutions apply, you will have to install it manually. Make sure Clang/LLVM 21 is in your path:

which clang-21

If not, run this to manually add it:

# use fish_add_path if you're using fish
# use path+="$(brew --prefix llvm@21)/bin" if you are using zsh
export PATH="$(brew --prefix llvm@21)/bin:$PATH"

# use fish_add_path if you're using fish
export PATH="$PATH:/usr/lib/llvm21/bin"

⚠️ Ubuntu distributions (<= 20.04) may require installation of the C++ standard library independently. See the troubleshooting section for more information.

Building Bun

After cloning the repository, run the following command to build. This may take a while as it will clone submodules and build dependencies.

bun run build

The binary will be located at ./build/debug/bun-debug. It is recommended to add this to your $PATH. To verify the build worked, let’s print the version number on the development build of Bun.

build/debug/bun-debug --version
x.y.z_debug

VSCode

VSCode is the recommended IDE for working on Bun, as it has been configured. Once opening, you can run Extensions: Show Recommended Extensions to install the recommended extensions for Rust and C++. rust-analyzer will pick up the workspace Cargo.toml automatically; the pinned toolchain in rust-toolchain.toml is used for analysis so diagnostics match the build. If you use a different editor, point rust-analyzer (or your editor’s Rust plugin) at the repo root — the Cargo workspace and rust-toolchain.toml are discovered automatically. We recommend adding ./build/debug to your $PATH so that you can run bun-debug in your terminal:

bun-debug

Running debug builds

The bd package.json script compiles and runs a debug build of Bun, only printing the output of the build process if it fails.

bun bd <args>
bun bd test foo.test.ts
bun bd ./foo.ts

A full debug build can take a few minutes when Rust or C++ has changed; cargo’s incremental compilation makes subsequent Rust-only rebuilds much faster. If your development workflow is “change one line, save, rebuild”, you will still spend too much time waiting for the link step. Instead:

Batch up your changes
Use cargo check -p <crate> (or bun run rust:check for the whole workspace) to type-check Rust changes without linking. bun run watch runs cargo check on every save.
Ensure rust-analyzer is running for inline diagnostics (if you use VSCode and install the recommended extensions, this should just work)
Prefer using the debugger (“CodeLLDB” in VSCode) to step through the code.
Use debug logs. BUN_DEBUG_<scope>=1 will enable debug logging for the corresponding declare_scope!(<scope>, ...) / scoped_log!(<scope>, ...) logs. You can also set BUN_DEBUG_QUIET_LOGS=1 to disable all debug logging that isn’t explicitly enabled. To dump debug logs into a file, BUN_DEBUG=<path-to-file>.log. Debug logs are aggressively removed in release builds.
src/js/**.ts changes are pretty much instant to rebuild. Single-crate Rust changes and C++ changes are incremental; only the final link is unavoidable.

Code generation scripts

Several code generation scripts are used during Bun’s build process. These are run automatically when changes are made to certain files. In particular, these are:

./src/codegen/generate-jssink.ts — Generates build/debug/codegen/JSSink.cpp, build/debug/codegen/JSSink.h which implement various classes for interfacing with ReadableStream. This is internally how FileSink, ArrayBufferSink, "type": "direct" streams and other code related to streams works.
./src/codegen/generate-classes.ts — Generates Rust & C++ bindings for JavaScriptCore classes implemented in Rust. In **/*.classes.ts files, we define the interfaces for various classes, methods, prototypes, getters/setters etc which the code generator reads to generate boilerplate code implementing the JavaScript objects in C++ and wiring them up to Rust.
./src/codegen/cppbind.ts — Scans the C++ bindings for functions marked with an export attribute and generates automatic Rust FFI wrappers (cpp.rs) for them.
./src/codegen/bundle-modules.ts — Bundles built-in modules like node:fs, bun:ffi into files we can include in the final binary. In development, these can be reloaded without rebuilding native code (you still need to run bun run build, but it re-reads the transpiled files from disk afterwards). In release builds, these are embedded into the binary.
./src/codegen/bundle-functions.ts — Bundles globally-accessible functions implemented in JavaScript/TypeScript like ReadableStream, WritableStream, and a handful more. These are used similarly to the builtin modules, but the output more closely aligns with what WebKit/Safari does for Safari’s built-in functions so that we can copy-paste the implementations from WebKit as a starting point.

Modifying ESM modules

Certain modules like node:fs, node:stream, bun:sqlite, and ws are implemented in JavaScript. These live in src/js/{node,bun,thirdparty} files and are pre-bundled using Bun.

Release build

To compile a release build of Bun, run:

bun run build:release

The binary will be located at ./build/release/bun and ./build/release/bun-profile.

Download release build from pull requests

To save you time spent building a release build locally, we provide a way to run release builds from pull requests. This is useful for manually testing changes in a release build before they are merged. To run a release build from a pull request, you can use the bun-pr npm package:

bunx bun-pr <pr-number>
bunx bun-pr <branch-name>
bunx bun-pr "https://github.com/oven-sh/bun/pull/1234566"
bunx bun-pr --asan <pr-number> # Linux x64 only

This will download the release build from the pull request and add it to $PATH as bun-${pr-number}. You can then run the build with bun-${pr-number}.

bun-1234566 --version

This works by downloading the release build from the GitHub Actions artifacts on the linked pull request. You may need the gh CLI installed to authenticate with GitHub.

Viewing CI failures from the terminal

Bun’s CI runs on BuildKite. Install the BuildKite CLI (brew install buildkite/buildkite/bk) and set BUILDKITE_API_TOKEN to a read-scoped API token. The repo includes a .bk.yaml so bk commands default to the bun pipeline.

bun run ci:status         # progress summary for the current branch's latest build
bun run ci:errors         # rendered test-failure output, tagged [new] vs [also on main]
bun run ci:logs           # save full logs for each failed job to ./tmp/ci-<build>/
bun run ci:watch          # watch until the build finishes
bun run ci:find           # print the build number (compose with raw `bk`)

All of these accept a target: #1234 (PR number), a PR URL, a branch name, or a build number. Without one they use the current git branch.

AddressSanitizer

AddressSanitizer helps find memory issues, and is enabled by default in debug builds of Bun on Linux and macOS. This covers the Rust code, the C++ bindings, and all dependencies. It makes the build take about 2x longer; if that’s stopping you from being productive you can disable it with bun run build:debug:noasan (or pass --asan=off to scripts/build.ts), but generally we recommend batching your changes up between builds. To build a release build with Address Sanitizer, run:

bun run build:asan

In CI, we run our test suite with at least one target that is built with Address Sanitizer.

Building WebKit locally + Debug mode of JSC

WebKit is not cloned by default (to save time and disk space). To clone and build WebKit locally, run:

# Clone WebKit into ./vendor/WebKit
git clone https://github.com/oven-sh/WebKit vendor/WebKit

# Check out the commit hash specified in WEBKIT_VERSION in scripts/build/deps/webkit.ts
git -C vendor/WebKit checkout <commit_hash>

# Build bun with the local JSC build — this automatically configures and builds JSC
bun run build:local

bun run build:local handles everything: configuring JSC, building JSC, and building Bun. On subsequent runs, JSC will incrementally rebuild if any WebKit sources changed. ninja -Cbuild/debug-local also works after the first build, and will build Bun+JSC. The build output goes to ./build/debug-local (instead of ./build/debug), so you’ll need to update a couple of places:

The first line in src/js/builtins.d.ts
The CompilationDatabase line in .clangd config should be CompilationDatabase: build/debug-local
In .vscode/launch.json, many configurations use ./build/debug/, change them as you see fit

Note that the WebKit folder, including build artifacts, is 8GB+ in size. If you are using a JSC debug build and using VScode, make sure to run the C/C++: Select a Configuration command to configure intellisense to find the debug headers. Note that if you make changes to our WebKit fork, you will also have to change WEBKIT_VERSION in scripts/build/deps/webkit.ts to point to the commit hash.

Troubleshooting

’span’ file not found on Ubuntu

⚠️ Please note that the instructions below are specific to issues occurring on Ubuntu. It is unlikely that the same issues will occur on other Linux distributions.

The Clang compiler typically uses the libstdc++ C++ standard library by default. libstdc++ is the default C++ Standard Library implementation provided by the GNU Compiler Collection (GCC). While Clang may link against the libc++ library, this requires explicitly providing the -stdlib flag when running Clang. Bun relies on C++20 features like std::span, which are not available in GCC versions lower than 11. GCC 10 doesn’t have all of the C++20 features implemented. As a result, running make setup may fail with the following error:

fatal error: 'span' file not found
#include <span>
         ^~~~~~

The issue may manifest when initially running bun setup as Clang being unable to compile a simple program:

The C++ compiler

  "/usr/bin/clang++-21"

is not able to compile a simple test program.

To fix the error, we need to update the GCC version to 11. To do this, we’ll need to check if the latest version is available in the distribution’s official repositories or use a third-party repository that provides GCC 11 packages. Here are general steps:

sudo apt update
sudo apt install gcc-11 g++-11
# If the above command fails with `Unable to locate package gcc-11` we need
# to add the APT repository
sudo add-apt-repository -y ppa:ubuntu-toolchain-r/test
# Now run `apt install` again
sudo apt install gcc-11 g++-11

Now, we need to set GCC 11 as the default compiler:

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-11 100
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-11 100

libarchive

If you see an error on macOS when compiling libarchive, run:

brew install pkg-config

macOS `library not found for -lSystem`

If you see this error when compiling, run:

xcode-select --install

Cannot find `libatomic.a`

Bun defaults to linking libatomic statically, as not all systems have it. If you are building on a distro that does not have a static libatomic available, you can run the following command to enable dynamic linking:

bun run build -DUSE_STATIC_LIBATOMIC=OFF

The built version of Bun may not work on other systems if compiled this way.

Using bun-debug

Disable logging: BUN_DEBUG_QUIET_LOGS=1 bun-debug ... (to disable all debug logging)
Enable logging for a specific scope: BUN_DEBUG_EventLoop=1 bun-debug ... (to enable scoped_log!(EventLoop, ...) output)
Bun transpiles every file it runs, to see the actual executed source in a debug build find it in /tmp/bun-debug-src/...path/to/file, for example the transpiled version of /home/bun/index.ts would be in /tmp/bun-debug-src/home/bun/index.ts

Get Started

Core Runtime

File & Module System

HTTP server

Networking

Data & Storage

Concurrency

Process & System

Interop & Tooling

Utilities

Standards & Compatibility

Contributing

Contributing

Using Nix (Alternative)

Install Dependencies (Manual)

Optional: Install `ccache`

Install LLVM

Building Bun

VSCode

Running debug builds

Code generation scripts

Modifying ESM modules

Release build

Download release build from pull requests

Viewing CI failures from the terminal

AddressSanitizer

Building WebKit locally + Debug mode of JSC

Troubleshooting

’span’ file not found on Ubuntu

libarchive

macOS `library not found for -lSystem`

Cannot find `libatomic.a`

Using bun-debug

​Using Nix (Alternative)

​Install Dependencies (Manual)

​Optional: Install ccache

​Install LLVM

​Building Bun

​VSCode

​Running debug builds

​Code generation scripts

​Modifying ESM modules

​Release build

​Download release build from pull requests

​Viewing CI failures from the terminal

​AddressSanitizer

​Building WebKit locally + Debug mode of JSC

​Troubleshooting

​’span’ file not found on Ubuntu

​libarchive

​macOS library not found for -lSystem

​Cannot find libatomic.a

​Using bun-debug

Using Nix (Alternative)

Install Dependencies (Manual)

Optional: Install `ccache`

Install LLVM

Building Bun

VSCode

Running debug builds

Code generation scripts

Modifying ESM modules

Release build

Download release build from pull requests

Viewing CI failures from the terminal

AddressSanitizer

Building WebKit locally + Debug mode of JSC

Troubleshooting

’span’ file not found on Ubuntu

libarchive

macOS `library not found for -lSystem`

Cannot find `libatomic.a`

Using bun-debug