38 lines
988 B
Groff
38 lines
988 B
Groff
|
.TH "NPM\-PACK" "1" "November 2019" "" ""
|
||
|
|
.SH "NAME"
|
||
|
|
\fBnpm-pack\fR \- Create a tarball from a package
|
||
|
|
.SS Synopsis
|
||
|
|
.P
|
||
|
|
.RS 2
|
||
|
|
.nf
|
||
|
|
npm pack [[<@scope>/]<pkg>\.\.\.] [\-\-dry\-run]
|
||
|
|
.fi
|
||
|
|
.RE
|
||
|
|
.SS Description
|
||
|
|
.P
|
||
|
|
For anything that's installable (that is, a package folder, tarball,
|
||
|
|
tarball url, name@tag, name@version, name, or scoped name), this
|
||
|
|
command will fetch it to the cache, and then copy the tarball to the
|
||
|
|
current working directory as \fB<name>\-<version>\.tgz\fP, and then write
|
||
|
|
the filenames out to stdout\.
|
||
|
|
.P
|
||
|
|
If the same package is specified multiple times, then the file will be
|
||
|
|
overwritten the second time\.
|
||
|
|
.P
|
||
|
|
If no arguments are supplied, then npm packs the current package folder\.
|
||
|
|
.P
|
||
|
|
The \fB\-\-dry\-run\fP argument will do everything that pack usually does without
|
||
|
|
actually packing anything\. Reports on what would have gone into the tarball\.
|
||
|
|
.SS See Also
|
||
|
|
.RS 0
|
||
|
|
.IP \(bu 2
|
||
|
|
npm help cache
|
||
|
|
.IP \(bu 2
|
||
|
|
npm help publish
|
||
|
|
.IP \(bu 2
|
||
|
|
npm help config
|
||
|
|
.IP \(bu 2
|
||
|
|
npm help npmrc
|
||
|
|
|
||
|
|
.RE
|