blob: 2034aac783e8bf36e1298bb3abdb86c3c0004184 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
npm-cache(1) -- install a package
===================================
## SYNOPSIS
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 [<name>[@<version>]]
## DESCRIPTION
* add:
Access the local cache of package data. 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.
If two arguments are provided, then npm will fetch the data from the
registry. This allows npm to use the filesystem as a local proxy to
the registry.
* ls:
Show the data in the cache. Additional arguments are joined together
in a path-like fashion, but something like `npm cache ls npm/0.1.5` is
acceptable as well.
* clean:
Delete data out of the cache for a specific package and version, all
versions of a package, or all data for all packages, depending on the
arguments supplied.
This can be used if invalid data gets into the cache.
## DETAILS
npm stores data for a version of a package in
`$ROOT/.npm/.cache/<name>/<version>`. Three pieces of data are stored
in this folder:
* 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.
## HISTORY
Added in npm version 0.1.6
|
