npm-cache(1) -- install a package
npm cache add <tarball file> npm cache add <folder> npm cache add <tarball url> npm cache add <name>@<version> npm cache ls [<path>] npm cache clean [<path>]
add: Add the specified package to the local cache. This command is primarily intended to be used internally by npm, but it can provide a way to add data to the local installation cache explicitly.
ls: Show the data in the cache. Argument is a path to show in the cache folder. Works a bit like the
findprogram, but limited by the
clean: Delete data out of the cache folder. If an argument is provided, then it specifies a subpath to delete. If no argument is provided, then the entire cache is cleared.
npm stores cache data in
$HOME/.npm. For each package that is added
to the cache, three pieces of information are stored in
- .../package/: A folder containing the package contents as they appear in the tarball.
- .../package.json: The package.json file, as npm sees it, with overlays applied and a _id attribute.
- .../package.tgz: The tarball for that version.
Additionally, whenever a registry request is made, a
is placed at the corresponding URI, to store the ETag and the requested
Commands that make non-essential registry requests (such as
view, or the completion scripts) generally specify a minimum timeout.
.cache.json file is younger than the specified timeout, then
they do not make an HTTP request to the registry.
$HOME/.npm on Posix, or
$HOME/npm-cache on Windows.
The root cache folder.