link-workspace-packages

To link workspace packages in a monorepo, configure dependencies between consumer and provider packages using your active package manager's workspace syntax. This updates package manifests and creates node_modules symlinks to ensure imports resolve correctly.

Workspace package imports fail when dependencies use incorrect workspace syntax or lack proper symlinks. You must detect the active package manager from the root lockfile and apply the correct workspace protocol to verify node_modules resolution.

Yes, you can use workspace linking for npm, yarn, pnpm, and bun monorepos. The linking process detects the active workspace manager from the root package.json or lockfile and applies the specific syntax required by each tool.

The best way to add new packages is to use workspace commands that automatically update package manifests to establish dependencies. This wires consumer and provider packages directly, avoiding manual tsconfig path mappings or package.json rewrites.

A workspace manager verifies dependencies are linked by checking that node_modules symlinks or hoists are created successfully. This ensures that imports resolve correctly across the workspace after applying the correct package manager syntax.