Bun Package Manager

by secondsky88378361314fMIT227 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago

Bun package manager commands (install, add, remove, update), workspaces, lockfiles, npm/yarn/pnpm migration. Use for dependency management with Bun.

Instructions onlySoftware Development
AI-generated overview

Reference guide for using Bun's package manager, covering install, add, remove, update, lockfiles, workspaces, and migration from npm, yarn, and pnpm.

What it does
This skill provides instructions and command references for managing JavaScript dependencies with Bun. It documents core commands such as bun install, bun add, bun remove, bun update, and bunx, along with installation flags, lockfile handling, workspace and monorepo configuration, lifecycle script trust settings, dependency overrides, non-npm dependency sources, installation strategies, CI/CD usage, platform-specific installs, common errors, and migration from npm, yarn, and pnpm. It also points to additional reference files for complete CLI flags, workspaces, and migration.
When to use it
Use it when working with Bun as a package manager: installing or updating dependencies, adding or removing packages, configuring lockfiles or workspaces, setting up monorepos, migrating a project from npm, yarn, or pnpm, or troubleshooting common dependency errors.
Requirements
No scripts are included; it is instructions only. It assumes Bun is installed and that the agent can run Bun CLI commands. Network access is needed for package installation. It references additional files (references/cli-commands.md, references/workspaces.md, references/migration.md) that are not present in the provided file list.

Bun Package Manager

Bun's package manager is a dramatically faster replacement for npm, yarn, and pnpm. Up to 25x faster than npm install.

Quick Start

bash
# Install all dependenciesbun install
# Add packagesbun add react react-dombun add -D typescript @types/react
# Remove packagesbun remove lodash
# Update packagesbun update
# Run package binariesbunx create-next-app

Core Commands

CommandDescription
bun installInstall all dependencies
bun add <pkg>Add dependency
bun add -D <pkg>Add dev dependency
bun add -O <pkg>Add optional dependency
bun add --peer <pkg>Add peer dependency
bun remove <pkg>Remove dependency
bun update [pkg]Update dependencies
bunx <pkg>Run package binary
bun pm cache rmClear cache

Installation Flags

bash
# Production mode (no devDependencies)bun install --production
# Frozen lockfile (CI/CD)bun install --frozen-lockfilebun ci  # shorthand
# Dry runbun install --dry-run
# Verbose/Silentbun install --verbosebun install --silent
# Force reinstallbun install --force
# Global packagesbun install -g cowsay

Lockfile

Bun uses bun.lock (text-based since v1.2):

bash
# Generate text lockfilebun install --save-text-lockfile
# Upgrade from binary bun.lockbbun install --save-text-lockfile --frozen-lockfile --lockfile-onlyrm bun.lockb

Workspaces (Monorepos)

json
{  "name": "my-monorepo",  "workspaces": ["packages/*", "apps/*"]}

Run commands across workspaces:

bash
# Run in matching packagesbun run --filter 'pkg-*' build
# Run in all workspacesbun run --filter '*' test
# Install for specific packagesbun install --filter 'pkg-a'

Lifecycle Scripts

Bun does not run lifecycle scripts from dependencies by default (security). Whitelist trusted packages:

json
{  "trustedDependencies": ["my-trusted-package"]}
bash
# Skip all lifecycle scriptsbun install --ignore-scripts
# Concurrent scriptsbun install --concurrent-scripts 5

Overrides & Resolutions

Force specific versions for nested dependencies:

json
{  "overrides": {    "lodash": "4.17.21"  }}

Yarn-style resolutions also supported:

json
{  "resolutions": {    "lodash": "4.17.21"  }}

Non-npm Dependencies

json
{  "dependencies": {    "dayjs": "git+https://github.com/iamkun/dayjs.git",    "lodash": "git+ssh://github.com/lodash/lodash.git#4.17.21",    "zod": "github:colinhacks/zod",    "react": "https://registry.npmjs.org/react/-/react-18.2.0.tgz",    "bun-types": "npm:@types/bun"  }}

Installation Strategies

Bun 1.3+ default flip: Starting in Bun 1.3, isolated is the default for workspaces (packages can no longer reach undeclared deps through the hoisted root node_modules). hoisted is now the legacy opt-out — only use it when a workspace package depends on a transitive dep that it doesn't declare.

Hoisted (legacy opt-out; still the default for single non-workspace packages)

Traditional flat node_modules:

bash
bun install --linker hoisted

Isolated (default for workspaces in Bun 1.3+)

pnpm-like strict isolation:

bash
bun install --linker isolated

Isolated prevents "phantom dependencies" - packages can only access declared dependencies. To make this explicit or restore it after an opt-out, set it in bunfig.toml:

toml
[install]linker = "isolated"   # default for workspaces in Bun 1.3+# linker = "hoisted"  # legacy opt-out

CI/CD

yaml
# GitHub Actions- uses: oven-sh/setup-bun@v2- run: bun ci  # frozen lockfile

Platform-Specific

bash
# Install for different platformbun install --cpu=x64 --os=linux

Secure Installation

When installing packages, follow supply chain security best practices:

  • Block post-install scripts — Bun disables them by default; allow specific packages via trustedDependencies in package.json
  • Cooldown period — Configure minimumReleaseAge in bunfig.toml to wait 7 days for new versions
  • Audit before installing — Run socket package score npm <pkg> or use socket npm install <pkg> to check packages before they reach your project

Load the dependency-upgrade skill for full security configuration including Socket CLI integration, cooldown setup, lockfile validation, and CI enforcement.

Common Errors

ErrorCauseFix
Cannot find moduleMissing dependencyRun bun install
Lockfile mismatchpackage.json changedRun bun install
Peer dependencyMissing peerbun add the peer
Lifecycle script failedUntrusted packageAdd to trustedDependencies

Migration from Other Package Managers

From pnpm

Bun automatically migrates pnpm-lock.yaml:

bash
bun install  # Auto-converts to bun.lock

Workspace config moves to package.json:

json
{  "workspaces": {    "packages": ["apps/*", "packages/*"],    "catalog": {      "react": "^18.0.0"    }  }}

From npm/Yarn

Simply run bun install - Bun reads package-lock.json and yarn.lock.

When to Load References

Load references/cli-commands.md when:

  • Need complete CLI flag reference
  • Working with advanced options

Load references/workspaces.md when:

  • Setting up monorepos
  • Configuring workspace filters

Load references/migration.md when:

  • Migrating from npm/yarn/pnpm
  • Converting lockfiles

Source and attribution

Source:secondsky/claude-skillsinplugins/bun/skills/bun-package-managerat commit8837836

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal