diff options
Diffstat (limited to 'deps/npm/man/man1/npm-publish.1')
| -rw-r--r-- | deps/npm/man/man1/npm-publish.1 | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/deps/npm/man/man1/npm-publish.1 b/deps/npm/man/man1/npm-publish.1 index 20133a4dfe..6a5c7265a6 100644 --- a/deps/npm/man/man1/npm-publish.1 +++ b/deps/npm/man/man1/npm-publish.1 @@ -1,4 +1,4 @@ -.TH "NPM\-PUBLISH" "1" "September 2022" "" "" +.TH "NPM\-PUBLISH" "1" "November 2022" "" "" .SH "NAME" \fBnpm-publish\fR \- Publish a package .SS Synopsis @@ -14,25 +14,25 @@ Publishes a package to the registry so that it can be installed by name\. .P By default npm will publish to the public registry\. This can be overridden by specifying a different default registry or using a -npm help \fBscope\fP in the name, combined with a +npm help scope in the name, combined with a scope\-configured registry (see -npm help \fBpackage\.json\fP)\. +\fBpackage\.json\fP \fI/configuring\-npm/package\-json)\fR\|\. .P A \fBpackage\fP is interpreted the same way as other commands (like \fBnpm install\fP and can be: .RS 0 .IP \(bu 2 a) a folder containing a program described by a -npm help \fBpackage\.json\fP file +\fBpackage\.json\fP \fI/configuring\-npm/package\-json\fR file .IP \(bu 2 b) a gzipped tarball containing (a) .IP \(bu 2 c) a url that resolves to (b) .IP \(bu 2 d) a \fB<name>@<version>\fP that is published on the registry (see -npm help \fBregistry\fP) with (c) +npm help registry) with (c) .IP \(bu 2 -e) a \fB<name>@<tag>\fP (see npm help \fBdist\-tag\fP) that +e) a \fB<name>@<tag>\fP (see npm help dist\-tag) that points to (d) .IP \(bu 2 f) a \fB<name>\fP that has a "latest" tag satisfying (e) @@ -46,13 +46,13 @@ exists in the specified registry\. .P Once a package is published with a given name and version, that specific name and version combination can never be used again, even if it is removed -with npm help \fBunpublish\fP\|\. +with npm help unpublish\. .P As of \fBnpm@5\fP, both a sha1sum and an integrity field with a sha512sum of the tarball will be submitted to the registry during publication\. Subsequent installs will use the strongest supported algorithm to verify downloads\. .P -Similar to \fB\-\-dry\-run\fP see npm help \fBpack\fP, which figures +Similar to \fB\-\-dry\-run\fP see npm help pack, which figures out the files to be included and packs them into a tarball to be uploaded to the registry\. .SS Files included in package @@ -66,7 +66,7 @@ are always included\. For example, \fBpackage\.json\fP, \fBREADME\.md\fP, \fBLICENSE\fP, and so on\. .IP \(bu 2 If there is a "files" list in -npm help \fBpackage\.json\fP, then only the files +\fBpackage\.json\fP \fI/configuring\-npm/package\-json\fR, then only the files specified will be included\. (If directories are specified, then they will be walked recursively and their contents included, subject to the same ignore rules\.) @@ -87,7 +87,7 @@ Symbolic links are never included in npm packages\. .RE .P -See npm help \fBdevelopers\fP for full details on what's +See npm help developers for full details on what's included in the published package, as well as details on how the package is built\. .SS Configuration @@ -230,7 +230,7 @@ This value is not exported to the environment for child processes\. .SS See Also .RS 0 .IP \(bu 2 -npm help package spec +npm help "package spec" .IP \(bu 2 npm\-packlist package \fIhttp://npm\.im/npm\-packlist\fR .IP \(bu 2 |