You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
|
|
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 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.
|
|
|
|
|
|
|
|
|
|
## SEE ALSO
|
|
|
|
|
|
|
|
|
|
* npm-publish(1)
|
|
|
|
|
* npm-registry(7)
|
