Library / Terminal & command line / Package manager
No. 104·noun·also called npm, npm install, yarn

Package manager

A tool that downloads and tracks the ready-made code libraries your project depends on.

SPECIMEN · DIAGRAM · FLOW
Datapackage.jsonwhat you need
Appnpm install
ServicePackage registry
Datanode_modulesinstalled code
readsdownloads
Definition

What it is

Projects rarely write everything from scratch. They pull in packages (also called libraries or dependencies): code for dates, charts, payments, and so on. A package manager installs them and records which versions you use.

For JavaScript it's usually npm (or yarn, pnpm). Python uses pip; Macs use Homebrew for installing tools. The list of what a project needs lives in a file like package.json, so anyone can recreate it with one command: npm install.

If an app won't start after you download it, a missing npm install is the most common reason.

Say it like a builder

How to ask for it

Vague

“Add something that does charts.”

Precise

“Add a charting package for a line chart of weekly signups. Recommend one well-maintained option, install it with npm, and tell me what it adds to package.json.”

Why it works

Naming the package manager and asking for a single justified choice keeps your project from collecting random dependencies.

In the wild

You've seen this in

  • Nnpm install in nearly every JavaScript README
  • PA huge node_modules folder in a project
  • Mbrew install in Mac setup guides
Usage note

Often confused with

IntegrationAn integration connects to an outside service at runtime; a package is code copied into your project.CLInpm itself is a CLI; the packages it installs are code your app uses.