summaryrefslogtreecommitdiff
path: root/deps/npm/man/man1/npm-deprecate.1
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/man/man1/npm-deprecate.1')
-rw-r--r--deps/npm/man/man1/npm-deprecate.110
1 files changed, 6 insertions, 4 deletions
diff --git a/deps/npm/man/man1/npm-deprecate.1 b/deps/npm/man/man1/npm-deprecate.1
index d146fe9ae6..be17e319c6 100644
--- a/deps/npm/man/man1/npm-deprecate.1
+++ b/deps/npm/man/man1/npm-deprecate.1
@@ -1,4 +1,4 @@
-.TH "NPM\-DEPRECATE" "1" "August 2018" "" ""
+.TH "NPM\-DEPRECATE" "1" "November 2018" "" ""
.SH "NAME"
\fBnpm-deprecate\fR \- Deprecate a version of a package
.SH SYNOPSIS
@@ -13,8 +13,8 @@ npm deprecate <pkg>[@<version>] <message>
This command will update the npm registry entry for a package, providing
a deprecation warning to all who attempt to install it\.
.P
-It works on version ranges as well as specific versions, so you can do
-something like this:
+It works on version ranges \fIhttps://semver\.npmjs\.com/\fR as well as specific
+versions, so you can do something like this:
.P
.RS 2
.nf
@@ -25,7 +25,9 @@ npm deprecate my\-thing@"< 0\.2\.3" "critical bug fixed in v0\.2\.3"
Note that you must be the package owner to deprecate something\. See the
\fBowner\fP and \fBadduser\fP help topics\.
.P
-To un\-deprecate a package, specify an empty string (\fB""\fP) for the \fBmessage\fP argument\.
+To un\-deprecate a package, specify an empty string (\fB""\fP) for the \fBmessage\fP
+argument\. Note that you must use double quotes with no space between them to
+format an empty string\.
.SH SEE ALSO
.RS 0
.IP \(bu 2