pnpm-monorepo-build

name: pnpm-monorepo-build description: Provide pnpm monorepo build commands and workflow guidance. Use when running package builds, filtered builds, or discussing build order.

pnpm Monorepo Build

Rule Anchor

• AGENTS.md > "Project Structure"
• AGENTS.md > "Build Requirements"

Scope

Use this skill to choose the correct pnpm build commands for the workspace.

Common Commands

pnpm --filter @robota-sdk/* build
pnpm --filter @robota-sdk/agent-core build
pnpm --filter @robota-sdk/agent-provider-openai build
pnpm --filter @robota-sdk/agent-team build
pnpm build

Build Order Notes

• Build core packages first (agents), then dependents.
• Use --filter to limit scope when possible.

Lifecycle Scripts (pre/post)

pnpm does not run npm-style pre<script>/post<script> hooks by default (enable-pre-post-scripts is off). A postbuild will silently never run from pnpm build, so any index/asset step defined that way is missing from the output.

• Chain the step explicitly in the script instead: "build": "next build && <step>".
• Make the step's tool a real devDependency (not an ambient/npx-fetched binary), so it resolves in CI.
• Verify the produced artifact exists (e.g. the generated file in out/), not just a zero exit code — a missing pre/post step does not fail the build.

Adding a Workspace Dependency

When adding (or removing) a workspace:* dependency between packages, edit the lockfile surgically — never regenerate it with a full pnpm install in a network-restricted/sandbox environment.

1. Edit the consumer package.json: add the dep under dependencies/devDependencies as "@robota-sdk/<pkg>": "workspace:*".
2. Apply a surgical pnpm-lock.yaml edit — add the entry to that package's dependencies: block:
   • specifier: workspace:*
   • version: link:../<pkg> for a sibling package, or link:../../packages/<pkg> for an app consuming a package.
3. Verify with pnpm install --frozen-lockfile — it must succeed without rewriting the lockfile.

NEVER commit a pnpm-lock.yaml that a full pnpm install regenerated in a network-restricted/sandbox env: it prunes the lockfile by thousands of lines (offline resolution drops unreachable registry entries), which is a corrupting change, not a real dependency update. If --frozen-lockfile fails, fix the surgical edit — never resolve it by regenerating the whole lockfile.

Verification

• Check exit codes and logs for build success.
• For dependency changes, confirm pnpm install --frozen-lockfile passes and the lockfile diff is limited to the intended dependencies: block.