link-workspace-packages

To fix "cannot find module" errors in a monorepo, you need to link workspace packages using your package manager's native workspace commands rather than manually editing tsconfig paths. This Skill detects your root package manager and executes the appropriate commands to wire dependencies automatically.

Linking dependencies between workspace packages in pnpm or yarn involves detecting the root lockfile and running the specific workspace command for that manager. This wires the provider package into the consumer without requiring manual package.json edits.

You do not need to manually edit tsconfig paths when adding a new package to an npm workspace. Instead, use the package manager's workspace commands to establish actual linking, which resolves inter-package dependencies properly.

The best way to wire inter-package dependencies after creating a new monorepo package is to use your package manager's workspace commands. This ensures node_modules contains the correct symlinks or workspace references to resolve imports.

Monorepo resolution errors like TS2307 occur because the new sibling package has not been wired as a dependency. Running the package manager's workspace commands links the provider package into the consumer, resolving the import error.

Yes, workspace linking validates that node_modules contains symlinks or workspace references after install. By executing the appropriate workspace commands, you confirm that inter-package dependencies resolve correctly across the monorepo.