summaryrefslogtreecommitdiff
path: root/deps/npm/docs/content/cli-commands/npm-deprecate.md
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/docs/content/cli-commands/npm-deprecate.md')
-rw-r--r--[-rwxr-xr-x]deps/npm/docs/content/cli-commands/npm-deprecate.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/deps/npm/docs/content/cli-commands/npm-deprecate.md b/deps/npm/docs/content/cli-commands/npm-deprecate.md
index 0a038e0255..d2d9613f65 100755..100644
--- a/deps/npm/docs/content/cli-commands/npm-deprecate.md
+++ b/deps/npm/docs/content/cli-commands/npm-deprecate.md
@@ -1,9 +1,9 @@
---
-section: cli-commands
+section: cli-commands
title: npm-deprecate
description: Deprecate a version of a package
---
-# npm-deprecate
+# npm-deprecate(1)
## Deprecate a version of a package
@@ -17,7 +17,7 @@ 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.
-It works on [version ranges](https://semver.npmjs.com/) as well as specific
+It works on [version ranges](https://semver.npmjs.com/) as well as specific
versions, so you can do something like this:
```bash
npm deprecate my-thing@"< 0.2.3" "critical bug fixed in v0.2.3"
@@ -26,8 +26,8 @@ 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
+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