pnpm

Files (15)

• GENERATION.md
• SKILL.md
• best-practices-ci.md · references/
• best-practices-migration.md · references/
• best-practices-performance.md · references/
• core-cli.md · references/
• core-config.md · references/
• core-store.md · references/
• core-workspaces.md · references/
• features-aliases.md · references/
• features-catalogs.md · references/
• features-hooks.md · references/
• features-overrides.md · references/
• features-patches.md · references/
• features-peer-deps.md · references/

SKILL.md (first lines)

pnpm is a fast, disk space efficient package manager. It uses a content-addressable store to deduplicate packages across all projects on a machine, saving significant disk space. pnpm enforces strict dependency resolution by default, preventing phantom dependencies. Configuration should preferably be placed in `pnpm-workspace.yaml` for pnpm-specific settings.

**Important:** When working with pnpm projects, agents should check for `pnpm-workspace.yaml` and `.npmrc` files to understand workspace structure and configuration. Always use `--frozen-lockfile` in CI environments.

> The skill is based on pnpm 10.x, generated at 2026-01-28.

## Core

| Topic         | Description                                                              | Reference                                        |
| ------------- | ------------------------------------------------------------------------ | ------------------------------------------------ |
| CLI Commands  | Install, add, remove, update, run, exec, dlx, and workspace commands     | [core-cli](references/core-cli.md)               |
| Configuration | pnpm-workspace.yaml, .npmrc settings, and package.json fields            | [core-config](references/core-config.md)         |
| Workspaces    | Monorepo support with filtering, workspace protocol, and shared lockfile | [core-workspaces](references/core-workspaces.md) |
| Store         | Content-addressable storage, hard links, and disk efficiency             | [core-store](references/core-store.md)           |

## Features

| Topic             | Description                                                  | Reference                                              |
| ----------------- | ------------------------------------------------------------ | ------------------------------------------------------ |
| Catalogs          | Centralized dependency version management for workspaces     | [features-catalogs](references/features-catalogs.md)   |
| Overrides         | Force specific versions of dependencies including transitive | [features-overrides](references/features-overrides.md) |
| Patches           | Modify third-party packages with custom fixes                | [features-patches](references/features-patches.md)     |
| Aliases           | Install packages under custom names using npm: protocol      | [features-aliases](references/features-aliases.md)     |
| Hooks             | Customize resolution with .pnpmfile.cjs hooks                | [features-hooks](references/features-hooks.md)         |
| Peer Dependencies | Auto-install, strict mode, and dependency rules              | [features-peer-deps](references/features-peer-deps.md) |

## Best practices

| Topic       | Description                                                        | Reference                                                              |
| ----------- | ------------------------------------------------------------------ | ---------------------------------------------------------------------- |
| CI/CD Setup | GitHub Actions, GitLab CI, Docker, and caching strategies          | [best-practices-ci](references/best-practices-ci.md)                   |
| Migration   | Migrating from npm/Yarn, handling phantom deps, monorepo migration | [best-practices-migration](references/best-practices-migration.md)     |
| Performance | Install optimizations, store caching, workspace parallelization    | [best-practices-performance](references/best-practices-performance.md) |

From yamcodes/arkenv, MIT.

More from yamcodes/arkenv