pnpm

Manage Node.js monorepo dependencies with pnpm and frozen-lockfile installs.

Updated Apr 6, 2022

Search Tags:#workspace #pnpm #monorepo #package-management #lockfile #dependency-resolution

Ready to run

npx skills add https://github.com/wjyugutou/study-test-demo --skill pnpm-wjyugutou

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pnpm
Source: https://github.com/wjyugutou/study-test-demo/tree/main/.trae/skills/pnpm
Command: npx skills add https://github.com/wjyugutou/study-test-demo --skill pnpm-wjyugutou

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

pnpm solves the challenges of deterministic, disk-space efficient dependency management for Node.js projects, particularly in monorepos with many packages.

Core Features & Use Cases

Deterministic installs: A single lockfile and content-addressable store ensure consistent installations across machines.
Strict dependency resolution: Prevents phantom dependencies and enforces explicit declarations.
Workspace support: Works with pnpm-workspace.yaml to manage multi-package repositories; supports catalogs and overrides.
Performance and storage efficiency: Disk-space savings via hard links and shared store.

Quick Start

Install dependencies: run pnpm install
Add a dependency: run pnpm add <pkg>
Run scripts across all workspaces: run pnpm -r run <script>

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 Node.js monorepo?▼

To manage dependencies in a monorepo, use a pnpm-workspace.yaml configuration to enable workspace-aware dependency installation, upgrading, and synchronization across all packages. This ensures consistent dependency management across your multi-package repository.

How does deterministic dependency resolution prevent phantom dependencies in Node.js?▼

Deterministic dependency resolution prevents phantom dependencies by enforcing strict explicit declarations, utilizing a content-addressable store and a single lockfile. This approach ensures that packages cannot access dependencies they have not explicitly declared.

What's the best way to run scripts across all workspaces in a monorepo?▼

The best way to run scripts across all workspaces is using the recursive command pnpm -r run <script>. This executes the specified script across every package defined in your pnpm-workspace.yaml configuration simultaneously.

Do I need a workspace configuration file to use pnpm for multi-package repositories?▼

Yes, you need a pnpm-workspace.yaml configuration file to manage multi-package repositories. This workspace configuration is required to enable workspace support, allowing pnpm to handle dependency installation and synchronization across packages.

How do frozen-lockfile semantics ensure reproducible builds in package management?▼

Frozen-lockfile semantics ensure reproducible builds by utilizing a single lockfile and a content-addressable store to guarantee consistent installations across machines. This prevents lockfile drift and ensures deterministic dependency resolution throughout the workspace.

Why does pnpm save disk space compared to other package management approaches?▼

pnpm saves disk space by using hard links and a shared content-addressable store for dependency installation. This approach avoids duplicating packages across multiple projects or workspaces, maximizing storage efficiency while maintaining strict dependency resolution.