summaryrefslogtreecommitdiff
path: root/deps/npm/man/man1/npm-publish.1
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/man/man1/npm-publish.1')
-rw-r--r--deps/npm/man/man1/npm-publish.127
1 files changed, 12 insertions, 15 deletions
diff --git a/deps/npm/man/man1/npm-publish.1 b/deps/npm/man/man1/npm-publish.1
index 410be8799b..45de41045e 100644
--- a/deps/npm/man/man1/npm-publish.1
+++ b/deps/npm/man/man1/npm-publish.1
@@ -1,7 +1,6 @@
-.TH "NPM\-PUBLISH" "" "November 2019" "" ""
+.TH "NPM\-PUBLISH" "1" "November 2019" "" ""
.SH "NAME"
-\fBnpm-publish\fR
-.SH Publish a package
+\fBnpm-publish\fR \- Publish a package
.SS Synopsis
.P
.RS 2
@@ -18,12 +17,10 @@ Publishes a package to the registry so that it can be installed by name\. All
files in the package directory are included if no local \fB\|\.gitignore\fP or
\fB\|\.npmignore\fP file exists\. If both files exist and a file is ignored by
\fB\|\.gitignore\fP but not by \fB\|\.npmignore\fP then it will be included\. See
-\fBnpm\-developers\fP \fI/docs/using\-npm/developers\fR for full details on what's included in the published
-package, as well as details on how the package is built\.
+npm help \fBdevelopers\fP for full details on what's included in the published package, as well as details on how the package is built\.
.P
By default npm will publish to the public registry\. This can be overridden by
-specifying a different default registry or using a \fBnpm\-scope\fP \fInpm\-scope\fR in the name
-(see \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json)\fR\|\.
+specifying a different default registry or using a npm help \fBscope\fP in the name (see npm help \fBpackage\.json\fP)\.
.RS 0
.IP \(bu 2
\fB<folder>\fP:
@@ -61,13 +58,13 @@ 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 \fBnpm\-unpublish\fP \fInpm\-unpublish\fR\|\.
+it is removed with npm help \fBunpublish\fP\|\.
.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 \fBnpm\-pack\fP \fInpm\-pack\fR, which figures out the files to be
+Similar to \fB\-\-dry\-run\fP see npm help \fBpack\fP, which figures out the files to be
included and packs them into a tarball to be uploaded to the registry\.
.SS See Also
.RS 0
@@ -76,16 +73,16 @@ npm help registry
.IP \(bu 2
npm help scope
.IP \(bu 2
-npm help npm\-adduser
+npm help adduser
.IP \(bu 2
-npm help npm\-owner
+npm help owner
.IP \(bu 2
-npm help npm\-deprecate
+npm help deprecate
.IP \(bu 2
-npm help npm\-dist\-tag
+npm help dist\-tag
.IP \(bu 2
-npm help npm\-pack
+npm help pack
.IP \(bu 2
-npm help npm\-profile
+npm help profile
.RE