link-workspace-packages

Automate workspace package linking across npm, yarn, pnpm, and bun.

11|5|Updated Jun 30, 2019
One-click install
npx skills add https://github.com/ikemtz/AngularMonoRepo --skill link-workspace-packages-ikemtz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/ikemtz/AngularMonoRepo/tree/main/src/.opencode/skills/link-workspace-packages
Command: npx skills add https://github.com/ikemtz/AngularMonoRepo --skill link-workspace-packages-ikemtz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Link workspace packages in monorepos across npm, yarn, pnpm, and bun to wire dependencies between packages and avoid manual edits to package.json or tsconfig paths.

Core Features & Use Cases

  • Detect the root workspace manager and apply the correct linking command
  • Link consumer to provider packages and ensure correct dependencies are recorded
  • Works across npm, yarn, pnpm, bun, with automatic local resolution

Quick Start

Identify the consumer and provider packages, then link them using the appropriate workspace command for your package manager.

Frequently Asked Questions about link-workspace-packages

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

FAQPage Schema
How do I link workspace packages in a monorepo?

To link workspace packages in a monorepo, automate the process by detecting the root package manager and updating consumer package.json files with workspace syntax. This wires dependencies without manual package.json or tsconfig edits.

Does this monorepo package linking work with npm, yarn, pnpm, and bun?

Yes, monorepo package linking works with npm, yarn, pnpm, and bun. It automatically detects your root workspace manager and applies the correct local resolution command to wire dependencies between consumer and provider packages.

How do I wire dependencies when adding new packages to a monorepo?

To wire dependencies when adding new packages to a monorepo, identify the consumer and provider packages and use the appropriate workspace command. This ensures proper dependency entries are recorded in the consumer package.json.

What's the best way to avoid manual package.json edits when linking local packages?

The best way to avoid manual package.json edits when linking local packages is automating workspace syntax updates. This detects the active package manager and executes manager-specific commands for local dependency resolution.

Why do I need to update consumer package.json with workspace syntax?

You need to update consumer package.json with workspace syntax to ensure correct local resolution of provider packages. This records accurate dependencies without requiring manual tsconfig path adjustments or breaking package manager conventions.