pnpm-workspace-migration

スター0

フォーク0

更新日2026年4月9日 22:01

Handle packages migrating between pnpm workspaces. Clean stale root copies, update workspace configs, fix broken workspace:* references.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

open-hax

open-hax/eta-mu-pi

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

pnpm Workspace Migration Protocol

Problem

When packages move between pnpm workspaces (e.g., from a root monorepo into a sub-monorepo), stale references accumulate in three places:

The old workspace's pnpm-workspace.yaml (explicit package paths)
Root package.json dependencies (workspace:* references)
Other packages' package.json that depend on the moved package via workspace:*

Steps

1. Identify Overlap

Find packages that exist in both locations:

comm -12 <(ls packages/ | sort) <(ls orgs/open-hax/openplanner/packages/ | sort)

2. Check References

Find who depends on the moved packages:

grep -r '"@scope/package-name"' --include='package.json' . | grep 'workspace:*'

3. Remove Stale Root Copies

If the old location was a git submodule: git submodule deinit -f packages/old-name
Remove the directory: rm -rf packages/old-name
Remove from pnpm-workspace.yaml if explicitly listed

4. Update Consumers

Root package.json scripts: update -C packages/old-name paths to new location
External packages: ensure the new workspace is listed in root pnpm-workspace.yaml

5. Workspace Discovery

pnpm does NOT auto-merge nested workspaces. If package X lives in orgs/repo/packages/X and the root workspace only lists orgs/repo, pnpm will NOT find X.
Fix by explicitly adding orgs/repo/packages/* to the root pnpm-workspace.yaml.

6. Broken Internal Deps

If the destination workspace has its own broken workspace:* deps, use --filter to install only the packages you need:

pnpm install --filter @scope/my-package...

The ... includes all dependencies and dependents of the filtered package.

Anti-Patterns

Running sudo rm -rf node_modules as a first step (indicates root-owned file contamination)
Adding symlinks to make packages appear in multiple workspace locations
Using shamefully-hoist=true to work around resolution issues

このリポジトリの他の Skills

同じリポジトリ

docker-no-root

open-hax/eta-mu-pi

Never run Docker containers as root. Enforce USER directive in Dockerfiles and user: in compose files. Database images are the only exception.

2026-04-090

session-source-recovery

open-hax/eta-mu-pi

Recover lost source files from pi session history when files were deleted but never committed to git.

2026-04-090

clock-model-evolver

open-hax/eta-mu-pi

Improve the Hormuz clock model through new signal classes, schema changes, uncertainty modeling, and better rendering or branch logic

2026-04-060

fork-tax-concurrent-agent-guardrails

open-hax/eta-mu-pi

Revise fork-tax protocols so they assume concurrent agents by default in shared workspaces, forbid destructive repo-wide cleanup of unrelated dirt, and require path-scoped staging plus explicit blocker recording.

2026-04-040

fork-tax

open-hax/eta-mu-pi

Persist the full working state into git (commit + tag + push + manifest artifacts) as a deterministic handoff snapshot. Use when the user requests Π / fork tax / full dump.

2026-04-040

atproto-auth-standardization

open-hax/eta-mu-pi

Standardize human login, service identity, and inter-service auth around AT Protocol DIDs and Bluesky-backed one-time sign-in, while removing host-local static secrets and bespoke per-service auth flows.

2026-03-210

name	pnpm-workspace-migration
description	Handle packages migrating between pnpm workspaces. Clean stale root copies, update workspace configs, fix broken workspace:* references.
triggers	["package moved","workspace migration","WORKSPACE_PKG_NOT_FOUND","pnpm-workspace.yaml","workspace:*"]

pnpm Workspace Migration Protocol

Problem

When packages move between pnpm workspaces (e.g., from a root monorepo into a sub-monorepo), stale references accumulate in three places:

The old workspace's pnpm-workspace.yaml (explicit package paths)
Root package.json dependencies (workspace:* references)
Other packages' package.json that depend on the moved package via workspace:*

Steps

1. Identify Overlap

Find packages that exist in both locations:

comm -12 <(ls packages/ | sort) <(ls orgs/open-hax/openplanner/packages/ | sort)

2. Check References

Find who depends on the moved packages:

grep -r '"@scope/package-name"' --include='package.json' . | grep 'workspace:*'

3. Remove Stale Root Copies

If the old location was a git submodule: git submodule deinit -f packages/old-name
Remove the directory: rm -rf packages/old-name
Remove from pnpm-workspace.yaml if explicitly listed

4. Update Consumers

Root package.json scripts: update -C packages/old-name paths to new location
External packages: ensure the new workspace is listed in root pnpm-workspace.yaml

5. Workspace Discovery

pnpm does NOT auto-merge nested workspaces. If package X lives in orgs/repo/packages/X and the root workspace only lists orgs/repo, pnpm will NOT find X.
Fix by explicitly adding orgs/repo/packages/* to the root pnpm-workspace.yaml.

6. Broken Internal Deps

If the destination workspace has its own broken workspace:* deps, use --filter to install only the packages you need:

pnpm install --filter @scope/my-package...

The ... includes all dependencies and dependents of the filtered package.

Anti-Patterns

Running sudo rm -rf node_modules as a first step (indicates root-owned file contamination)
Adding symlinks to make packages appear in multiple workspace locations
Using shamefully-hoist=true to work around resolution issues