Technology & Testing Core B · Official guidance Platform: Web

npm

npm is a JavaScript package registry and command-line tool. It installs, lists, and publishes packages, and runs project scripts.

See how it works
You might call it Node package managernpm registrynpm CLI

See how it works

Original worked examplenpm

Another example

CI runs npm ci from the committed lockfile and runs the test script. It gets the same dependency tree as local checks.

Main parts

  1. 01Code or behavior under test
  2. 02Observable evidence
  3. 03Coverage, failure, and recovery

Use it when

Use it for Node dependencies and shared project scripts. Review and commit the lockfile on purpose.

Do not use it when

Do not mix package managers, ignore install scripts, publish secrets, or change lockfiles by accident.

Name used in code

package.json + package-lock.json + npm ci

Before you ship

Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback.

Request you can copy

Outcome: Use or review npm as a technical building block that the team can maintain. User context: CI runs npm ci from the committed lockfile and runs the test script. It gets the same dependency tree as local checks. Technology or engineering concept: npm. Why it fits: Use it for Node dependencies and shared project scripts. Review and commit the lockfile on purpose. Do not use it when: Do not mix package managers, ignore install scripts, publish secrets, or change lockfiles by accident. Engineering fit: Define where it runs and which version to use. Set its job, interfaces, data flow, dependencies, supported systems, security, and speed limits. Explain how it fits the current stack. Lifecycle safeguards: Check dependency health and licenses. Add monitoring and a fallback. Name the upgrade owner. Do not add a second tool for the same job without a measured benefit. Acceptance criteria: A small integration proves the needed behavior. Test compatibility, security, failure, and performance. Document deploy, upgrade, support, and rollback steps. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Current stack, runtime and version rules, target systems, dependency owner, performance budget, support period, and migration limits.

Check this request

Review the current use of npm. Definition: npm is a JavaScript package registry and command-line tool. It installs, lists, and publishes packages, and runs project scripts. Release checks: Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

B
How official is this term?

Official guidance

The named platform, framework, project, or expert group has an official guide for this term.

It is official for that source. Other platforms or teams may use the term in another way.

Scope
npm
Document status
stable
Checked on
2026-07-30

Evidence sources & scope

Authority source · npm · stable npm Documentation Scope: npm Role here: Authority within stated scope Source covers: canonical name, definition, platform API, implementation, usage guidance

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.