summaryrefslogtreecommitdiff
path: root/deps/npm/docs/content/cli-commands/npm-deprecate.md
blob: 0a038e0255d5e09cbfc661901f92986cb9d39274 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
---
section: cli-commands
title: npm-deprecate
description: Deprecate a version of a package
---
# npm-deprecate

## Deprecate a version of a package

### Synopsis
```bash
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:
```bash
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](/cli-commands/npm-publish)
* [npm registry](/using-npm/registry)