1 ---
2 title: npm-deprecate
3 section: 1
4 description: Deprecate a version of a package
5 github_repo: npm/cli
6 github_branch: release/v6
7 github_path: docs/content/commands/npm-deprecate.md
8 redirect_from:
9 - /cli-documentation/v6/cli-commands/deprecate
10 - /cli-documentation/v6/cli-commands/npm-deprecate
11 - /cli-documentation/v6/commands/deprecate
12 - /cli-documentation/v6/commands/npm-deprecate
13 - /cli-documentation/v6/deprecate
14 - /cli-documentation/v6/npm-deprecate
15 - /cli/v6/cli-commands/deprecate
16 - /cli/v6/cli-commands/npm-deprecate
17 - /cli/v6/commands/deprecate
18 - /cli/v6/deprecate
19 - /cli/v6/npm-deprecate
20 ---
21
22 ### Synopsis
23
24 ```bash
25 npm deprecate <pkg>[@<version>] <message>
26 ```
27
28 ### Description
29
30 This command will update the npm registry entry for a package, providing a deprecation warning to all who attempt to install it.
31
32 It works on [version ranges](https://semver.npmjs.com/) as well as specific versions, so you can do something like this:
33
34 ```bash
35 npm deprecate my-thing@"< 0.2.3" "critical bug fixed in v0.2.3"
36 ```
37
38 Note that you must be the package owner to deprecate something. See the `owner` and `adduser` help topics.
39
40 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.
41
42 ### See Also
43
44 - [npm publish](/cli/v6/commands/npm-publish)
45 - [npm registry](/cli/v6/using-npm/registry)