pnpm-package-managerlisted

# pnpm Package Manager ## Overview pnpm best practices for frontend projects: - pnpm commands (add, remove, update, run) - `.npmrc` configuration - Lock file management - CI/CD integration - Workspace support (monorepos) - Troubleshooting common issues --- ## Hard Rules <HARD-RULES> These rules are NON-NEGOTIABLE. Violating any of them is a bug. - ALWAYS use `pnpm` for all package operations — NEVER `npm` or `yarn` in pnpm projects - ALWAYS use `pnpm run` to execute scripts — NEVER `npm run` or `yarn` - ALWAYS commit `pnpm-lock.yaml` — the lock file MUST be in version control - ALWAYS use `pnpm dlx` instead of `npx` for one-off package execution - ALWAYS use `--frozen-lockfile` in CI — NEVER allow lock file modifications in CI - NEVER delete `pnpm-lock.yaml` to "fix" issues — resolve the underlying problem - NEVER use `shamefully-hoist=true` unless absolutely required by a broken dependency - ALWAYS check for existing lock file before running `pnpm install` in a new project </HARD-RULES> --- ## Detecting pnpm Projects Before using pnpm commands, verify the project uses pnpm: ```bash # Check for pnpm lock file ls pnpm-lock.yaml # Check for pnpm workspace ls pnpm-workspace.yaml # Verify pnpm is available pnpm --version ``` **If `pnpm-lock.yaml` exists → use pnpm. If `package-lock.json` exists → use npm. If `yarn.lock` exists → use yarn.** Never mix package managers. --- ## Essential Commands ### Installing Dependencies ```bash # Install all dependencies from l