link-workspace-packages

Links workspace packages in monorepos across npm, yarn, pnpm, and bun.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/vinhgiang/pet-store --skill link-workspace-packages-vinhgiang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/vinhgiang/pet-store/tree/main/.cursor/skills/link-workspace-packages
Command: npx skills add https://github.com/vinhgiang/pet-store --skill link-workspace-packages-vinhgiang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of linking packages within a monorepo, resolving dependency issues that arise when working with multiple interconnected packages.

Core Features & Use Cases

  • Package Linking: Connects consumer packages to provider packages using the appropriate syntax for npm, yarn, pnpm, and bun.
  • Dependency Resolution: Fixes "cannot find module" and similar resolution errors by ensuring correct workspace linking.
  • Use Case: After creating a new shared UI component package, use this Skill to link it to your main application package, ensuring all components are correctly recognized and available.

Quick Start

Use the link-workspace-packages skill to add the '@org/ui' package as a dependency to the '@org/app' package using pnpm.

Frequently Asked Questions about link-workspace-packages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix 'cannot find module' errors when linking monorepo workspace packages?

Proper workspace package linking resolves 'cannot find module' errors by ensuring correct dependency wiring across monorepo packages using package manager-specific commands for deterministic resolution.

How do I link a shared package to my main application across different package managers?

Linking a shared package across npm, yarn, pnpm, or bun requires using package manager-specific workspace commands to connect consumer packages to provider packages, ensuring all components are correctly recognized and available.

Does this workspace linking approach work with both pnpm and bun?

Yes, workspace linking works with pnpm and bun. It utilizes package manager-specific workspace commands across npm, yarn, pnpm, and bun to ensure deterministic linking and resolve dependency issues in interconnected packages.

What is the best way to automate dependency wiring for interconnected packages in a monorepo?

Automating dependency wiring in a monorepo is best handled by utilizing package manager-specific workspace commands for deterministic linking, which addresses common resolution errors by ensuring proper connections between interconnected packages.

Why does my monorepo fail to resolve dependencies after adding a new shared UI component package?

Monorepos fail to resolve dependencies when workspace packages are not properly linked. Connecting the consumer application package to the new provider package using the correct syntax for npm, yarn, pnpm, or bun ensures components are correctly recognized.