link-workspace-packages

Linking workspace packages requires updating package.json with the appropriate workspace syntax for your package manager, then running installation to generate symlinks in node_modules that resolve inter-package dependencies correctly.

Workspace package resolution errors typically occur when package.json lacks the correct workspace syntax or symlinks are missing in node_modules. Applying the appropriate workspace syntax for your package manager and verifying symlinks after installation resolves these errors.

When generating a new package in a monorepo, the best approach is to apply the appropriate workspace syntax in package.json based on your detected package manager, ensuring sibling package imports resolve reliably without manual edits.

Yes, this approach works across different package managers by detecting the active package manager and applying the correct workspace syntax to package.json, ensuring symlinks are properly generated and verified in node_modules.

To verify symlinks in node_modules after linking workspace packages, run the installation command from the consumer directory and check that the generated symlinks correctly point to the provider package directories for @org/* imports.