from small one page howto to huge articles all in one place

search text in:




Other .linuxhowtos.org sites:gentoo.linuxhowtos.org



Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

210204

userrating:


May 25th. 2007:
Words

486

Views

259174

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

150540

userrating:


April, 26th. 2006:

Druckversion
You are here: manpages





NP-CACHE

Section: (1)
Updated: October 2025
Index Return to Main Contents
 

NAME

np-cache- Manipulates packages cache  

Synopsis

npm cache add <packag-spec>
npm cache clean [lB]<key>[rB]
npm cache ls [lB]<name>@<version>[rB]
npm cache verify
npm cache npx ls
npm cache npx rm [lB]<key>...[rB]
npm cache npx info <key>...
Note: This command is unaware of workspaces.  

Description

Used to add, list, or clean the npm cache folder. Also used to view info about entries in the npm exec (aka npx) cache folder.  

npm cache

*
add: Add the specified packages 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.
*
clean: Delete a single entry or all entries out of the cache folder. Note that this is typically unnecessary, as npm's cache is sel-healing and resistant to data corruption issues.
*
ls: List given entries or all entries in the local cache.
*
verify: Verify the contents of the cache folder, garbage collecting any unneeded data, and verifying the integrity of the cache index and all cached data.

 

npm cache npx

*
ls: List all entries in the npx cache.
*
rm: Remove given entries or all entries from the npx cache.
*
info: Get detailed information about given entries in the npx cache.

 

Details

npm stores cache data in an opaque directory within the configured cache, named _cacache. This directory is a [rs]fBcacache[rs]fR lahttp://npm.im/cacachera-based conten-addressable cache that stores all http request data as well as other packag-related data. This directory is primarily accessed through pacote, the library responsible for all package fetching as of npm@5. All data that passes through the cache is fully verified for integrity on both insertion and extraction. Cache corruption will either trigger an error, or signal to pacote that the data must be refetched, which it will do automatically. For this reason, it should never be necessary to clear the cache for any reason other than reclaiming disk space, thus why clean now requires -force to run. There is currently no method exposed through npm to inspect or directly manage the contents of this cache. In order to access it, cacache must be used directly. npm will not remove data by itself: the cache will grow as new packages are installed.  

A note about the cache's design

The npm cache is strictly a cache: it should not be relied upon as a persistent and reliable data store for package data. npm makes no guarantee that a previousl-cached piece of data will be available later, and will automatically delete corrupted contents. The primary guarantee that the cache makes is that, if it does return data, that data will be exactly the data that was inserted. To run an offline verification of existing cache contents, use npm cache verify.  

Configuration

 

cache

*
Default: Windows: %LocalAppData%[rs]np-cache, Posix: ~/.npm
*
Type: Path

The location of npm's cache directory.  

See Also

*
npm help "package spec"
*
npm help folders
*
npm help config
*
npm help npmrc
*
npm help install
*
npm help publish
*
npm help pack
*
npm help exec
*
https://npm.im/cacache
*
https://npm.im/pacote
*
https://npm.im/@npmcli/arborist
*
https://npm.im/mak-fetc-happen


 

Index

NAME
Synopsis
Description
npm cache
npm cache npx
Details
A note about the cache's design
Configuration
cache
See Also





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2025 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 12.3 ms