link-workspace-packages

Two pieces of code sitting in the same repository, one needing the other: this wires them together the way that repository's tooling expects, so the import points at the copy next door rather than a published one.

WHEN TO USE

SCOPE

USE FOR

Add a shared internal library as a dependency of an app inside a monorepo.
Work out which package manager a repo uses before wiring up a new dependency.
Fix a missing-module error caused by a package that was never linked as a workspace dependency.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (9)

Link Workspace Packages

Add dependencies between packages in a monorepo. All package managers support workspaces but with different syntax.

Detect Package Manager

Check whether there's a packageManager field in the root-level package.json.

Alternatively check lockfile in repo root:

pnpm-lock.yaml → pnpm
yarn.lock → yarn
bun.lock / bun.lockb → bun
package-lock.json → npm

Workflow

Identify consumer package (the one importing)
Identify provider package(s) (being imported)
Add dependency using package manager's workspace syntax
Verify symlinks created in consumer's node_modules/

pnpm

Uses workspace: protocol - symlinks only created when explicitly declared.

# From consumer directory
pnpm add @org/ui --workspace

# Or with --filter from anywhere
pnpm add @org/ui --filter @org/app --workspace

Result in package.json:

{ "dependencies": { "@org/ui": "workspace:*" } }

yarn (v2+/berry)

Also uses workspace: protocol.

yarn workspace @org/app add @org/ui

Result in package.json:

{ "dependencies": { "@org/ui": "workspace:^" } }

npm

No workspace: protocol. npm auto-symlinks workspace packages.

npm install @org/ui --workspace @org/app

Result in package.json:

{ "dependencies": { "@org/ui": "*" } }

npm resolves to local workspace automatically during install.

bun

Supports workspace: protocol (pnpm-compatible).

cd packages/app && bun add @org/ui

Result in package.json:

{ "dependencies": { "@org/ui": "workspace:*" } }

Examples

Example 1: pnpm - link ui lib to app

pnpm add @org/ui --filter @org/app --workspace

Example 2: npm - link multiple packages

npm install @org/data-access @org/ui --workspace @org/dashboard

Example 3: Debug "Cannot find module"

Check if dependency is declared in consumer's package.json
If not, add it using appropriate command above
Run install (pnpm install, npm install, etc.)

Notes

Symlinks appear in <consumer>/node_modules/@org/<package>
Hoisting differs by manager:
- npm/bun: hoist shared deps to root node_modules
- pnpm: no hoisting (strict isolation, prevents phantom deps)
- yarn berry: uses Plug'n'Play by default (no node_modules)
Root package.json should have "private": true to prevent accidental publish

Local tool required

1 FOR YOU

01
Have an existing monorepo workspace
Have Node.js with pnpm, yarn, npm, or bun installed, and already be inside a monorepo workspace with a root package.json — the skill only wires a dependency between packages that already exist.

This skill ships inside the Nx AI Agent Skills plugin. Listed package contents include 1 agent. Installed components and skill versions may vary by AI tool.

Install just this skill

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add nrwl/nx-ai-agents-config --skill "link-workspace-packages" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

Install the whole plugin

This route installs the Nx AI Agent Skills plugin package selected for your AI tool.

PLUGIN MARKETPLACE

Add the marketplace, then install the plugin

Typed inside the agent's own prompt, not in a terminal. The marketplace is called nx-claude-plugins, which is the part after the @.

01

/plugin marketplace add nrwl/nx-ai-agents-config

02
```
/plugin install nx@nx-claude-plugins
```

Open plugin page ↗

View on GitHub

The repository is licensed under MIT — use, modification, and redistribution are allowed under that license’s terms.

View the repository’s license file on GitHub →

Link Workspace Packages

Detect Package Manager

Workflow

pnpm

yarn (v2+/berry)

npm

bun

Examples

Notes

Local tool required

Install just this skill

Install the whole plugin

Add the marketplace, then install the plugin

More skills

monitor-ci

nx-cloud-api

nx-cloud-cache-investigator

nx-cloud-ci-failure-review

nx-generate

nx-import