Bun

bun add

To add a particular package:

bun add preact

To specify a version, version range, or tag:

bun add zod@3.20.0
bun add zod@^3.0.0
bun add zod@latest

--dev

Alias--development, -d, -D

To add a package as a dev dependency ("devDependencies"):

bun add --dev @types/react
bun add -d @types/react

--optional

To add a package as an optional dependency ("optionalDependencies"):

bun add --optional lodash

--peer

To add a package as a peer dependency ("peerDependencies"):

bun add --peer @types/bun

--exact

Alias-E

To add a package and pin to the resolved version, use --exact. This will resolve the version of the package and add it to your package.json with an exact version number instead of a version range.

bun add react --exact
bun add react -E

This will add the following to your package.json:

{
  "dependencies": {
    // without --exact
    "react": "^18.2.0", // this matches >= 18.2.0 < 19.0.0

    // with --exact
    "react": "18.2.0" // this matches only 18.2.0 exactly
  }
}

To view a complete list of options for this command:

bun add --help

--global

Note — This would not modify package.json of your current project folder. Alias - bun add --global, bun add -g, bun install --global and bun install -g

To install a package globally, use the -g/--global flag. This will not modify the package.json of your current project. Typically this is used for installing command-line tools.

bun add --global cowsay # or `bun add -g cowsay`
cowsay "Bun!"
 ______
< Bun! >
 ------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||

Configuring global installation behavior

Trusted dependencies

Unlike other npm clients, Bun does not execute arbitrary lifecycle scripts for installed dependencies, such as postinstall. These scripts represent a potential security risk, as they can execute arbitrary code on your machine.

To tell Bun to allow lifecycle scripts for a particular package, add the package to trustedDependencies in your package.json.

{
  "name": "my-app",
  "version": "1.0.0",
  "trustedDependencies": ["my-trusted-package"]
}

Bun reads this field and will run lifecycle scripts for my-trusted-package.

Git dependencies

To add a dependency from a public or private git repository:

bun add git@github.com:moment/moment.git

Note — To install private repositories, your system needs the appropriate SSH credentials to access the repository.

Bun supports a variety of protocols, including github, git, git+ssh, git+https, and many more.

{
  "dependencies": {
    "dayjs": "git+https://github.com/iamkun/dayjs.git",
    "lodash": "git+ssh://github.com/lodash/lodash.git#4.17.21",
    "moment": "git@github.com:moment/moment.git",
    "zod": "github:colinhacks/zod"
  }
}

Tarball dependencies

A package name can correspond to a publicly hosted .tgz file. During installation, Bun will download and install the package from the specified tarball URL, rather than from the package registry.

bun add zod@https://registry.npmjs.org/zod/-/zod-3.21.4.tgz

This will add the following line to your package.json:

package.json
{
  "dependencies": {
    "zod": "https://registry.npmjs.org/zod/-/zod-3.21.4.tgz"
  }
}

CLI Usage

$bun add <package> <@version>

Flags

Lockfile Options

-y,--yarn
Write a yarn.lock file (yarn v1)
--no-save
Don't update package.json or save a lockfile
--save
Save to package.json (true by default)
--frozen-lockfile
Disallow changes to lockfile
--save-text-lockfile
Save a text-based lockfile
--lockfile-only
Generate a lockfile without installing dependencies

Dependency Types

-p,--production
Don't install devDependencies
-d,--dev
Add dependency to "devDependencies"
--optional
Add dependency to "optionalDependencies"
--peer
Add dependency to "peerDependencies"

Security and Trust

--ca=<val>
Provide a Certificate Authority signing certificate
--cafile=<val>
The same as `--ca`, but is a file path to the certificate
--no-verify
Skip verifying integrity of newly downloaded packages
--trust
Add to trustedDependencies in the project's package.json and install the package(s)

Installation Behavior

--dry-run
Don't install anything
-f,--force
Always request the latest versions from the registry & reinstall all dependencies
--ignore-scripts
Skip lifecycle scripts in the project's package.json (dependency scripts are never run)
--only-missing
Only add dependencies to package.json if they are not already present

Caching and Performance

--cache-dir=<val>
Store & load cached data from a specific directory path
--no-cache
Ignore manifest cache entirely
--backend=<val>
Platform-specific optimizations for installing dependencies. Possible values: "clonefile" (default), "hardlink", "symlink", "copyfile"
--concurrent-scripts=<val>
Maximum number of concurrent jobs for lifecycle scripts (default 5)
--network-concurrency=<val>
Maximum number of concurrent network requests (default 48)

Logging and Output

--silent
Don't log anything
--verbose
Excessively verbose logging
--no-progress
Disable the progress bar
--no-summary
Don't print a summary

Configuration

-c,--config=<val>
Specify path to config file (bunfig.toml)
--registry=<val>
Use a specific registry by default, overriding .npmrc, bunfig.toml and environment variables
--omit=<val>
Exclude 'dev', 'optional', or 'peer' dependencies from install

Workspace

-g,--global
Install globally
--cwd=<val>
Set a specific cwd

Misc

-E,--exact
Add the exact version instead of the ^range
-a,--analyze
Recursively analyze & install dependencies of files passed as arguments (using Bun's bundler)
-h,--help
Print this help menu

Examples

Add a dependency from the npm registry
bun add zod
bun add zod@next
Add a dev, optional, or peer dependency
bun add -d typescript
bun add --optional lodash
Full documentation is available at https://bun.sh/docs/cli/add