Bun Workspace Config Generator

Bun workspaces let you manage multiple packages in a single monorepo. You define workspace packages in the root package.json using the 'workspaces' field, and Bun links them together so they can reference each other as local dependencies. This is similar to npm/yarn workspaces but with Bun's speed advantage.

bunfig.toml is Bun's configuration file. It controls install behavior (registry, frozen lockfile, production mode), test settings (timeout, preload files), and runtime options. Think of it as the Bun equivalent of .npmrc but with more features and TOML format.

In bunfig.toml you can set per-scope registries under [install.scopes]. For example, '@mycompany' packages can be resolved from a private registry while everything else uses npm. Each scope can have its own url, token, and username settings.

With --frozen-lockfile (or frozenLockfile = true in bunfig.toml), Bun will fail if the lockfile needs to be updated — it only installs exactly what's already locked. This is the recommended setting for CI environments to ensure reproducible builds and catch accidental dependency changes.

Yes. In a Bun workspace, each package can have its own tsconfig.json with path aliases. The root tsconfig can extend or reference child configs using TypeScript project references. Bun respects tsconfig paths natively without extra plugins.

The workspaces field in package.json supports standard glob patterns: 'packages/*' matches all direct subdirectories of packages/, 'apps/**' matches any depth, and explicit paths like 'packages/utils' for specific packages. Bun follows the same workspace protocol as Yarn and npm.