Bun Workspace Generator

A Bun workspace is a monorepo where multiple packages share a single root node_modules and package.json. Define it with the 'workspaces' field in root package.json: { "workspaces": ["packages/*"] }. Bun automatically links local packages — if packages/web depends on @myorg/shared, Bun symlinks it from the workspace without publishing to npm. Run scripts across all packages: 'bun run --filter "*" build'. This is faster than npm/yarn workspaces due to Bun's native package manager.

bunfig.toml is Bun's configuration file for install behavior, test runner settings, and runtime options. The [install] section configures registry, scoped registries, and install flags. The [test] section sets test timeout, preload files, and coverage settings. The [run] section controls script execution. Unlike package.json engines or .npmrc, bunfig.toml is Bun-specific and lives at the root of your project or in ~/.bunfig.toml for global config.

bun.lock is Bun's binary lockfile format — significantly smaller and faster to read/write than JSON-based lockfiles. It records exact resolved package versions and integrity hashes. Use 'bun install --frozen-lockfile' in CI to fail if the lockfile would change. If you need npm/yarn compatibility (e.g., for Vercel or other platforms that call npm install), set 'bun install --save-text-lockfile' to generate a text-format lockfile, or commit package-lock.json alongside bun.lock.

The --filter flag selects which workspace packages to run a script in. 'bun run --filter "*" build' runs the 'build' script in all packages that have it. 'bun run --filter "frontend" dev' runs only in the 'frontend' package (matched by name field). You can also use glob patterns: 'bun run --filter "@myorg/*" test'. Bun runs these in parallel by default and respects workspace dependency order for build scripts.

bun build is the fastest option and works well for server-side bundles (Bun runtime target) and simple browser bundles. vite is the best choice for frontend apps with hot module replacement, CSS handling, and the rich plugin ecosystem. tsup (powered by esbuild) is ideal for library packages that need dual CJS+ESM output, TypeScript declarations, and tree-shakeable builds. For a monorepo: use bun build or tsup for shared/library packages and vite for frontend apps.