pnpm

Manage monorepo dependencies with pnpm workspaces and strict resolution.

Updated Jan 23, 2024
One-click install
npx skills add https://github.com/TeamMagicOfConch/conch --skill pnpm-teammagicofconch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pnpm
Source: https://github.com/TeamMagicOfConch/conch/tree/main/.agents/skills/pnpm
Command: npx skills add https://github.com/TeamMagicOfConch/conch --skill pnpm-teammagicofconch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

pnpm provides fast, deterministic dependency management for multi-package repositories, reducing duplication and improving install reliability across teams.

Core Features & Use Cases

  • Monorepo support with workspaces using pnpm-workspace.yaml and catalogs for centralized version management.
  • Strict dependency resolution, preventing phantom dependencies and enabling predictable builds.
  • Efficient store usage and hoisting strategies to speed up installs in large repos.
  • Use Case: bootstrap a new monorepo, install dependencies, and build all packages with minimal friction.

Quick Start

Run pnpm install at the repository root to initialize dependencies and run a workspace build to verify integration.

Frequently Asked Questions about pnpm

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

FAQPage Schema
How do I manage dependencies across multiple packages in a monorepo?

Monorepo dependency management uses a workspace file to define packages and centralize versions. This enables shared resolution, workspace bootstrapping, and consistent installs across all sub-packages.

What is the best way to prevent phantom dependencies in a multi-package repository?

Preventing phantom dependencies requires strict resolution that isolates package scopes. By enforcing explicit declarations and avoiding global hoisting, it ensures predictable builds and prevents access to undeclared packages.

How do I bootstrap a new monorepo and install all workspace dependencies?

To bootstrap a monorepo, run install at the repository root to initialize dependencies using the shared content-addressable store. Then execute a workspace build to verify integration and confirm setup.

Can I use catalogs and overrides to centralize version management in a workspace?

Catalogs and overrides centralize version management by allowing shared dependency versions across workspace packages. This mechanism enforces consistent versions and allows targeted patches without modifying individual package configurations.

Does strict dependency resolution and a shared store speed up installs in large repositories?

Strict resolution and a shared content-addressable store speed up installs in large repos by minimizing duplication and optimizing hoisting strategies. This reduces disk usage and improves install reliability across teams.