dependency-manager

To enforce cataloged dependencies in a Bun monorepo, run the provided check scripts to validate root and workspace package.json files against the workspaces.catalog, detect hardcoded versions, and report actionable violations.

Dependency version drift occurs when different workspace packages use varying versions of the same library. Centralize versions in the root workspaces.catalog and validate package.json files to eliminate hard-coded versions and prevent drift.

Yes, you can automatically fix hardcoded dependency versions by running the fix script, which applies updates across the repository to align all workspace package.json files with the centralized root catalog entries.

Yes, Bun is required as the runtime dependency to execute the scripts that validate root and workspace package.json files and enforce catalog-based dependency management across the monorepo.

The best way to centralize package versions is using a root workspaces.catalog, which allows you to manage versions in one place and validate all workspace package.json files to ensure consistency and eliminate inappropriate workspace refs.

Catalog validation reports missing catalog entries when workspace package.json files contain dependencies not registered in the root workspaces.catalog, identifying hardcoded versions or inappropriate workspace refs that require updating.