link-workspace-packages

Linking workspace packages in a monorepo requires correctly declaring dependencies in package.json and ensuring proper symlinking. This skill automates that wiring by adapting to your specific package manager's workspace protocol for seamless internal package resolution.

Yes, monorepo linking works with pnpm, yarn, npm, and bun. The skill is package manager agnostic and adapts to each tool's specific workspace protocol, ensuring correct symlinking and dependency declaration across all supported environments.

The best way to add a newly generated package as a dependency to a sibling is to use an automated linking tool. This skill resolves dependency wiring issues by correctly declaring the internal package reference in your package.json according to your package manager's workspace protocol.

Importing a sibling package fails when dependencies are not correctly wired or symlinked in your package.json. This skill solves package resolution issues by ensuring dependencies between internal monorepo packages are properly declared and resolvable by your package manager.

You need workspace protocols for monorepo package linking when setting up dependencies between internal packages. This skill ensures correct symlinking and dependency declaration according to each package manager's specific workspace protocol, enabling cross-package dependency management.

Yes, you can manage cross-package dependencies without manual symlinking. This skill automates the process of linking packages within a monorepo, ensuring that internal dependencies are correctly set up and resolvable by your package manager.