/home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1/
/home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1
NameSizeModeActions
npm-access.140620644editdlrm
npm-adduser.119920644editdlrm
npm-audit.1173810644editdlrm
npm-bugs.133790644editdlrm
npm-cache.131320644editdlrm
npm-ci.1101810644editdlrm
npm-completion.19970644editdlrm
npm-config.146360644editdlrm
npm-dedupe.198620644editdlrm
npm-deprecate.118920644editdlrm
npm-diff.197710644editdlrm
npm-dist-tag.156360644editdlrm
npm-docs.133610644editdlrm
npm-doctor.153720644editdlrm
npm-edit.111800644editdlrm
npm-exec.1124910644editdlrm
npm-explain.129370644editdlrm
npm-explore.110890644editdlrm
npm-find-dupes.175900644editdlrm
npm-fund.140540644editdlrm
npm-help-search.18670644editdlrm
npm-help.110990644editdlrm
npm-hook.127080644editdlrm
npm-init.1111030644editdlrm
npm-install-ci-test.183200644editdlrm
npm-install-test.1111490644editdlrm
npm-install.1269640644editdlrm
npm-link.1129500644editdlrm
npm-login.123450644editdlrm
npm-logout.118870644editdlrm
npm-ls.194190644editdlrm
npm-org.123100644editdlrm
npm-outdated.163770644editdlrm
npm-owner.133630644editdlrm
npm-pack.138760644editdlrm
npm-ping.18490644editdlrm
npm-pkg.187040644editdlrm
npm-prefix.113170644editdlrm
npm-profile.134210644editdlrm
npm-prune.164570644editdlrm
npm-publish.183090644editdlrm
npm-query.176880644editdlrm
npm-rebuild.156640644editdlrm
npm-repo.131430644editdlrm
npm-restart.117090644editdlrm
npm-root.111940644editdlrm
npm-run-script.183770644editdlrm
npm-sbom.189960644editdlrm
npm-search.139520644editdlrm
npm-shrinkwrap.110040644editdlrm
npm-star.118070644editdlrm
npm-stars.17950644editdlrm
npm-start.118350644editdlrm
npm-stop.114660644editdlrm
npm-team.145030644editdlrm
npm-test.113790644editdlrm
npm-token.131860644editdlrm
npm-uninstall.149860644editdlrm
npm-unpublish.149000644editdlrm
npm-unstar.116580644editdlrm
npm-update.1132230644editdlrm
npm-version.177550644editdlrm
npm-view.161460644editdlrm
npm-whoami.18730644editdlrm
npm.159470644editdlrm
npx.164070644editdlrm
Edit: /home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1/npm-cache.1 (3132B)
.TH "NPM-CACHE" "1" "July 2024" "NPM@10.8.2" "" .SH "NAME" \fBnpm-cache\fR - Manipulates packages cache .SS "Synopsis" .P .RS 2 .nf npm cache add npm cache clean \[lB]\[rB] npm cache ls \[lB]@\[rB] npm cache verify .fi .RE .P Note: This command is unaware of workspaces. .SS "Description" .P Used to add, list, or clean the npm cache folder. .RS 0 .IP \(bu 4 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. .IP \(bu 4 clean: Delete all data out of the cache folder. Note that this is typically unnecessary, as npm's cache is self-healing and resistant to data corruption issues. .IP \(bu 4 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. .RE 0 .SS "Details" .P npm stores cache data in an opaque directory within the configured \fBcache\fR, named \fB_cacache\fR. This directory is a \fB\fBcacache\fR\fR \fI\(lahttp://npm.im/cacache\(ra\fR-based content-addressable cache that stores all http request data as well as other package-related data. This directory is primarily accessed through \fBpacote\fR, the library responsible for all package fetching as of npm@5. .P 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 \fBpacote\fR 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 \fBclean\fR now requires \fB--force\fR to run. .P There is currently no method exposed through npm to inspect or directly manage the contents of this cache. In order to access it, \fBcacache\fR must be used directly. .P npm will not remove data by itself: the cache will grow as new packages are installed. .SS "A note about the cache's design" .P 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 previously-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. .P To run an offline verification of existing cache contents, use \fBnpm cache verify\fR. .SS "Configuration" .SS "\fBcache\fR" .RS 0 .IP \(bu 4 Default: Windows: \fB%LocalAppData%\[rs]npm-cache\fR, Posix: \fB~/.npm\fR .IP \(bu 4 Type: Path .RE 0 .P The location of npm's cache directory. .SS "See Also" .RS 0 .IP \(bu 4 npm help "package spec" .IP \(bu 4 npm help folders .IP \(bu 4 npm help config .IP \(bu 4 npm help npmrc .IP \(bu 4 npm help install .IP \(bu 4 npm help publish .IP \(bu 4 npm help pack .IP \(bu 4 https://npm.im/cacache .IP \(bu 4 https://npm.im/pacote .IP \(bu 4 https://npm.im/@npmcli/arborist .IP \(bu 4 https://npm.im/make-fetch-happen .RE 0