Angular Package Manager

When to Use

• Adding, removing, or updating npm packages in an Angular project or workspace
• Listing outdated packages and planning version bumps
• Verifying a specific package version exists before bumping it
• Upgrading Angular itself or Angular ecosystem libraries (which ship migration schematics)
• Working in an Angular monorepo / npm workspace

Prerequisites

• Node.js and npm installed (a version compatible with the target Angular version; see the project's engines field and package.json).
• npm available on your PATH. If the repo uses pnpm or yarn, match the existing package manager and lockfile instead (see pnpm / yarn Repos below).
• Angular CLI (ng) available (via npx ng or a local devDependency) for ng add / ng update.

Core Rules