pnpm-workspace-catalog

Centralize and enforce cross-package dependency versions in a pnpm workspace with catalog strict mode.

Updated Jan 23, 2025
One-click install
npx skills add https://github.com/ymkz/demo-monorepo --skill pnpm-workspace-catalog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pnpm-workspace-catalog
Source: https://github.com/ymkz/demo-monorepo/tree/main/.agents/skills/pnpm-workspace-catalog
Command: npx skills add https://github.com/ymkz/demo-monorepo --skill pnpm-workspace-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PNPM workspace centralizes and enforces dependency versions across multiple packages using a catalog with strict mode, preventing drift and incompatible upgrades.

Core Features & Use Cases

  • Centralized catalog: define and lock shared dependency versions across apps/packages.
  • Strict mode: only catalog-defined versions are allowed, triggering errors for mismatches.
  • Streamlined upgrades: update a single catalog entry to apply across the monorepo.

Quick Start

Configure your pnpm-workspace.yaml to enable catalog and set catalogMode: strict for unified dependency management.

Frequently Asked Questions about pnpm-workspace-catalog

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

FAQPage Schema
How do I centralize dependency versions across a pnpm monorepo?▼

To centralize dependency versions in a pnpm workspace, configure the pnpm-workspace.yaml file to use a catalog. This locks shared dependency versions across all apps and packages, preventing version drift and incompatible upgrades.

What is pnpm catalog strict mode and how does it prevent dependency drift?▼

Pnpm catalog strict mode enforces unified dependency management by only allowing catalog-defined versions. It triggers errors for any version mismatches, actively preventing drift and incompatible upgrades across the monorepo.

How do I set up a shared dependency catalog using pnpm-workspace.yaml?▼

You set up a shared dependency catalog by configuring pnpm-workspace.yaml and enabling the catalog feature. Set catalogMode to strict within this file to enforce unified dependency management across your workspace packages.

Can I enforce unified upgrades for multiple packages in a pnpm workspace?▼

Yes, you can enforce unified upgrades in a pnpm workspace using a centralized catalog with strict mode. Updating a single catalog entry applies the version change across the entire monorepo, streamlining the upgrade process.

What format does the SKILL.md file require for pnpm workspace tooling integration?▼

The SKILL.md file requires YAML frontmatter containing the name and description fields for proper tooling integration. This metadata supports the catalog configuration and strict mode enforcement within the pnpm workspace.