link-workspace-packages

To fix 'cannot find module' errors, link workspace packages in your monorepo by detecting the root package manager and applying its specific workspace syntax to wire consumer and provider dependencies. This resolves cross-package imports.

Add a sibling package as a dependency by identifying the consumer and provider packages, then running the appropriate workspace command from the consumer directory to apply the correct pnpm or yarn workspace syntax.

Yes, the workspace linking approach works with npm, pnpm, yarn, and bun by detecting the active root package manager and applying the correct workspace-specific syntax to wire the monorepo packages.

TypeScript shows TS2307 'failed to resolve import' when workspace packages are not properly wired. Linking the provider package to the consumer ensures symlinks exist in node_modules, resolving the module path.

The best way to verify workspace links is to check that the symlinks exist in the consumer package's node_modules directory after applying the package manager's workspace commands to wire the new packages.

Manually link workspace packages when you create or generate new packages, need to add a sibling dependency, or encounter resolution errors like 'cannot find module' that standard installs fail to resolve.