npm-cache

Add a specific package to the cache

$ npm cache add [package_name]

$ npm cache clean [key]

$ npm cache clean [[-f|--force]]

$ npm cache ls

$ npm cache ls [name]@[version]

$ npm cache verify

$ npm cache npx ls

npm cache add <path>
npm cache clean [--force]
npm cache verify

add <path>
    Add specified tarball path to the cache

clean [--force]
    Remove all cache data; --force required since npm 5.0.0

verify
    Check cache integrity, remove invalid/unneeded files

--cache <path>
    Set custom cache directory

--force
    Bypass safety checks for clean operation

The npm cache command manages the directory where npm stores downloaded package tarballs to accelerate future installations. This cache prevents redundant downloads, improving efficiency across projects.

Key subcommands include add, which manually places a tarball into the cache; clean, which removes all cache data to free disk space; and verify, which scans for corruption, removes invalid files, and ensures consistency.

By default on Linux, the cache resides at ~/.npm, which can expand significantly with heavy usage. Cleaning does not impact node_modules directories or global installs—only cached archives. Since npm 5.0.0, clean requires --force for safety. The --cache option overrides the location, useful for custom setups or CI environments.

This command is essential for maintenance, troubleshooting install issues, or managing storage on cache-heavy systems.

Cleaning cache triggers re-downloads on next install, increasing bandwidth use. Does not affect installed packages. Use verify first for partial cleanup.

Linux/Unix: ~/.npm
View with npm config get cache

Can grow to GBs; monitor with du -sh ~/.npm
Regular verify prevents bloat without full clean.

Part of npm since v1.x; npm 5.0.0 (2017) added --force requirement for clean to prevent data loss. Evolved with scoped packages and better verification in npm 6+.

npm(1)