/
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
mkdir
upload
Name
Size
Mode
Actions
npm-access.1
4062
0644
edit
dl
rm
npm-adduser.1
1992
0644
edit
dl
rm
npm-audit.1
17381
0644
edit
dl
rm
npm-bugs.1
3379
0644
edit
dl
rm
npm-cache.1
3132
0644
edit
dl
rm
npm-ci.1
10181
0644
edit
dl
rm
npm-completion.1
997
0644
edit
dl
rm
npm-config.1
4636
0644
edit
dl
rm
npm-dedupe.1
9862
0644
edit
dl
rm
npm-deprecate.1
1892
0644
edit
dl
rm
npm-diff.1
9771
0644
edit
dl
rm
npm-dist-tag.1
5636
0644
edit
dl
rm
npm-docs.1
3361
0644
edit
dl
rm
npm-doctor.1
5372
0644
edit
dl
rm
npm-edit.1
1180
0644
edit
dl
rm
npm-exec.1
12491
0644
edit
dl
rm
npm-explain.1
2937
0644
edit
dl
rm
npm-explore.1
1089
0644
edit
dl
rm
npm-find-dupes.1
7590
0644
edit
dl
rm
npm-fund.1
4054
0644
edit
dl
rm
npm-help-search.1
867
0644
edit
dl
rm
npm-help.1
1099
0644
edit
dl
rm
npm-hook.1
2708
0644
edit
dl
rm
npm-init.1
11103
0644
edit
dl
rm
npm-install-ci-test.1
8320
0644
edit
dl
rm
npm-install-test.1
11149
0644
edit
dl
rm
npm-install.1
26964
0644
edit
dl
rm
npm-link.1
12950
0644
edit
dl
rm
npm-login.1
2345
0644
edit
dl
rm
npm-logout.1
1887
0644
edit
dl
rm
npm-ls.1
9419
0644
edit
dl
rm
npm-org.1
2310
0644
edit
dl
rm
npm-outdated.1
6377
0644
edit
dl
rm
npm-owner.1
3363
0644
edit
dl
rm
npm-pack.1
3876
0644
edit
dl
rm
npm-ping.1
849
0644
edit
dl
rm
npm-pkg.1
8704
0644
edit
dl
rm
npm-prefix.1
1317
0644
edit
dl
rm
npm-profile.1
3421
0644
edit
dl
rm
npm-prune.1
6457
0644
edit
dl
rm
npm-publish.1
8309
0644
edit
dl
rm
npm-query.1
7688
0644
edit
dl
rm
npm-rebuild.1
5664
0644
edit
dl
rm
npm-repo.1
3143
0644
edit
dl
rm
npm-restart.1
1709
0644
edit
dl
rm
npm-root.1
1194
0644
edit
dl
rm
npm-run-script.1
8377
0644
edit
dl
rm
npm-sbom.1
8996
0644
edit
dl
rm
npm-search.1
3952
0644
edit
dl
rm
npm-shrinkwrap.1
1004
0644
edit
dl
rm
npm-star.1
1807
0644
edit
dl
rm
npm-stars.1
795
0644
edit
dl
rm
npm-start.1
1835
0644
edit
dl
rm
npm-stop.1
1466
0644
edit
dl
rm
npm-team.1
4503
0644
edit
dl
rm
npm-test.1
1379
0644
edit
dl
rm
npm-token.1
3186
0644
edit
dl
rm
npm-uninstall.1
4986
0644
edit
dl
rm
npm-unpublish.1
4900
0644
edit
dl
rm
npm-unstar.1
1658
0644
edit
dl
rm
npm-update.1
13223
0644
edit
dl
rm
npm-version.1
7755
0644
edit
dl
rm
npm-view.1
6146
0644
edit
dl
rm
npm-whoami.1
873
0644
edit
dl
rm
npm.1
5947
0644
edit
dl
rm
npx.1
6407
0644
edit
dl
rm
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 <package-spec> npm cache clean \[lB]<key>\[rB] npm cache ls \[lB]<name>@<version>\[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
Save
cmd:
run