link-workspace-packages

To link workspace packages in a monorepo and resolve resolution errors, you need to wire dependencies between consumer and provider packages using your package manager's workspace commands to update manifests and create symlinks.

Yes, workspace linking works with pnpm, npm, yarn, and bun by detecting the active package manager and applying the correct workspace syntax to establish dependencies and ensure cross-package import resolution.

The best way to wire dependencies between consumer and provider packages is to run the workspace command from the consumer package, which updates manifests with workspace:* or equivalent syntax to establish correct dependencies.

Resolution errors for workspace packages occur when dependencies between consumer and provider packages are not properly wired, requiring you to update manifests and verify symlinks in node_modules for correct inter-package resolution.

Workspace-aware linking verifies symlinks in node_modules by checking that the package manager's workspace commands have correctly established dependencies, ensuring cross-package import resolution across all projects in the monorepo.

No, you do not need to manually edit package.json or tsconfig paths when linking workspace packages, because the process automatically updates manifests using the package manager's workspace syntax to establish dependencies.