pnpm

Managing dependencies in a monorepo uses a content-addressable store to deduplicate packages and enforce strict dependency resolution. This prevents phantom dependencies, saves disk space, and ensures deterministic installs across all workspace packages.

The best way to prevent phantom dependencies is using a content-addressable package store that enforces strict dependency resolution. This ensures packages only access dependencies explicitly declared in their manifest, maintaining strict isolation across workspace projects.

To set up pnpm workspaces, define your packages in a root-level pnpm-workspace.yaml file. Running pnpm install at the repository root processes all workspace dependencies, and you can use pnpm run to execute scripts across the monorepo.

Yes, you can use catalogs, overrides, and patches to control dependency versions across workspace packages. These features allow you to centrally manage and patch dependencies, ensuring version consistency and applying targeted fixes across your monorepo.

You can configure CI-friendly installs by running pnpm install with the --frozen-lockfile flag. This enforces deterministic installs by relying strictly on the existing lockfile, preventing unintended dependency updates during automated CI pipelines.

pnpm saves disk space across multiple projects by using a centralized, content-addressable store. Instead of duplicating packages for each project, it links them from a global store, significantly reducing disk usage for monorepos and overlapping codebases.