mirror of
https://github.com/nodejs/node.git
synced 2025-05-15 11:36:57 +00:00
4a3ccd8938
PR-URL: https://github.com/nodejs/node/pull/32368 Refs: https://github.com/nodejs/node/issues/32296 Reviewed-By: Bradley Farias <bradley.meck@gmail.com> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
37 lines
949 B
Markdown
37 lines
949 B
Markdown
---
|
|
section: cli-commands
|
|
title: npm-deprecate
|
|
description: Deprecate a version of a package
|
|
---
|
|
# npm-deprecate(1)
|
|
|
|
## 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/publish)
|
|
* [npm registry](/using-npm/registry)
|