1 files changed, 28 insertions, 0 deletions
diff --git a/deps/node/deps/npm/doc/cli/npm-deprecate.md b/deps/node/deps/npm/doc/cli/npm-deprecate.md
new file mode 100644
index 00000000..ea1ab3a2
--- /dev/null
+++ b/deps/node/deps/npm/doc/cli/npm-deprecate.md
@@ -0,0 +1,28 @@
+npm-deprecate(1) -- Deprecate a version of a package
+====================================================
+
+## SYNOPSIS
+
+    npm deprecate <pkg>[@<version>] <message>
+
+## DESCRIPTION
+
+This command will update the npm registry entry for a package, providing
+a deprecation warning to all who attempt to install it.
+
+It works on [version ranges](https://semver.npmjs.com/) as well as specific
+versions, so you can do something like this:
+
+    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
+`owner` and `adduser` help topics.
+
+To un-deprecate a package, specify an empty string (`""`) for the `message`
+argument. Note that you must use double quotes with no space between them to
+format an empty string.
+
+## SEE ALSO
+
+* npm-publish(1)
+* npm-registry(7)