link-workspace-packages

Fix cannot find module errors in a monorepo by declaring and linking sibling workspace packages so local packages are discoverable at install time. This resolves missing imports by symlinking the provider package into the consumer package.

Link workspace packages by detecting the package manager from the root package.json packageManager field or lockfile, then running manager-specific workspace add or install commands that produce the appropriate workspace protocol entries or local installs.

Yes, workspace linking works with npm, pnpm, yarn (berry), and bun. It applies manager-specific semantics to add dependencies, ensuring the consumer package references the provider package with the correct workspace protocol or install behavior.

You need to declare workspace dependencies after creating a new package so local sibling packages are properly symlinked and discoverable. Without declaring them, import resolution fails because the package manager cannot find the local provider package.

Verify workspace symlinks were created by checking for workspace protocol entries or local installs in the consumer package. Verification guidance explains hoisting differences across managers to help you avoid phantom dependency issues.

The best way to add a sibling package as a dependency is to run the corresponding workspace add command from the repository root after detecting your package manager, which links the provider package into the consumer package using the correct workspace protocol.