link-workspace-packages

To link workspace packages in a monorepo, run your package manager's workspace add command from the consumer package directory to wire dependencies on the provider package, resolving errors like cannot find module or TS2307.

Errors like TS2307 or cannot find module occur because workspace dependencies are not linked. You must use your package manager's workspace commands to establish the actual link rather than patching tsconfig paths.

Yes, workspace linking works across pnpm, yarn, npm, and bun. The process detects your active workspace manager by inspecting the root package.json or lockfiles and applies the correct linking patterns for that specific tool.

The best way to wire up newly created packages is using your package manager's native workspace workflow to add dependencies, which properly links the packages instead of relying on manual package.json edits or tsconfig path aliases.

No, you should not edit tsconfig paths to resolve imports between workspace packages. You should enforce using the package manager's workspace commands to fix actual linking instead of patching configurations or manually editing package.json.