Installation

Bun ships as a single executable with no dependencies that can be installed a few different ways.

Installing

macOS and Linux

curl -fsSL https://bun.sh/install | bash # for macOS, Linux, and WSL

# to install a specific version

curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.10"

npm install -g bun # the last `npm` command you'll ever need

brew install oven-sh/bun/bun # for macOS and Linux

docker pull oven/bun

docker run --rm --init --ulimit memlock=-1:-1 oven/bun

Windows

To install, paste this into a terminal:

powershell -c "irm bun.sh/install.ps1|iex"

npm install -g bun # the last `npm` command you'll ever need

scoop install bun

For support and discussion, please join the #windows channel on our Discord.

Docker

Bun provides a Docker image that supports both Linux x64 and arm64.

docker pull oven/bun

docker run --rm --init --ulimit memlock=-1:-1 oven/bun

There are also image variants for different operating systems.

docker pull oven/bun:debian

docker pull oven/bun:slim

docker pull oven/bun:distroless

docker pull oven/bun:alpine

Checking installation

To check that Bun was installed successfully, open a new terminal window and run bun --version.

bun --version

1.x.y

To see the precise commit of oven-sh/bun that you're using, run bun --revision.

bun --revision

1.x.y+b7982ac13189

If you've installed Bun but are seeing a command not found error, you may have to manually add the installation directory (~/.bun/bin) to your PATH.

How to add your PATH

echo $SHELL

/bin/zsh # or /bin/bash or /bin/fish

# add to ~/.zshrc
export BUN_INSTALL="$HOME/.bun"
export PATH="$BUN_INSTALL/bin:$PATH"

# add to ~/.bashrc
export BUN_INSTALL="$HOME/.bun"
export PATH="$BUN_INSTALL/bin:$PATH"

# add to ~/.config/fish/config.fish
export BUN_INSTALL="$HOME/.bun"
export PATH="$BUN_INSTALL/bin:$PATH"

& "$env:USERPROFILE\.bun\bin\bun" --version

[System.Environment]::SetEnvironmentVariable(
    "Path",
    [System.Environment]::GetEnvironmentVariable("Path", "User") + ";$env:USERPROFILE\.bun\bin",
    [System.EnvironmentVariableTarget]::User
)

Upgrading

Once installed, the binary can upgrade itself.

bun upgrade

Canary builds

Bun automatically releases an (untested) canary build on every commit to main. To upgrade to the latest canary build:

bun upgrade --canary

The canary build is useful for testing new features and bug fixes before they're released in a stable build. To help the Bun team fix bugs faster, canary builds automatically upload crash reports to Bun's team.

View canary build

Installing older versions of Bun

Since Bun is a single binary, you can install older versions of Bun by re-running the installer script with a specific version.

Installing a specific version of Bun on Linux/Mac

To install a specific version of Bun, you can pass the git tag of the version you want to install to the install script, such as bun-v1.2.0 or bun-v1.2.10.

curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.10"

Installing a specific version of Bun on Windows

On Windows, you can install a specific version of Bun by passing the version number to the Powershell install script.

# PowerShell:

iex "& {$(irm https://bun.sh/install.ps1)} -Version 1.2.10"

Downloading Bun binaries directly

To download Bun binaries directly, you can visit the releases page page on GitHub.

For convenience, here are download links for the latest version:

• bun-linux-x64.zip
• bun-linux-x64-baseline.zip
• bun-linux-x64-musl.zip
• bun-linux-x64-musl-baseline.zip
• bun-windows-x64.zip
• bun-windows-x64-baseline.zip
• bun-darwin-aarch64.zip
• bun-linux-aarch64.zip
• bun-linux-aarch64-musl.zip
• bun-darwin-x64.zip

The musl binaries are built for distributions that do not ship with the glibc libraries by default, instead relying on musl. The two most popular distros are Void Linux and Alpine Linux, with the latter is used heavily in Docker containers. If you encounter an error like the following: bun: /lib/x86_64-linux-gnu/libm.so.6: version GLIBC_2.29' not found (required by bun), try using the musl binary. Bun's install script automatically chooses the correct binary for your system.

Bun's x64 binaries target the Haswell CPU architecture, which means they require AVX and AVX2 instructions. For Linux and Windows, the x64-baseline binaries are also available which target the Nehalem architecture. If you run into an "Illegal Instruction" error when running Bun, try using the baseline binaries instead. Bun's install scripts automatically chooses the correct binary for your system which helps avoid this issue. Baseline builds are slower than regular builds, so use them only if necessary.

Bun also publishes darwin-x64-baseline binaries, but these are just a copy of the darwin-x64 ones so they still have the same CPU requirement. We only maintain these since some tools expect them to exist. Bun requires macOS 13.0 or later, which does not support any CPUs that don't meet our requirement.

Uninstall

If you need to remove Bun from your system, use the following commands.

rm -rf ~/.bun # for macOS, Linux, and WSL

powershell -c ~\.bun\uninstall.ps1

scoop uninstall bun

npm uninstall -g bun

brew uninstall bun