table of contents
- bullseye 7.5.2+ds-2
- bullseye-backports 8.5.5~ds1-1~bpo11+1
- testing 9.1.3~ds1-1
- unstable 9.2.0~ds1-1
NPM-DEPRECATE(1) | NPM-DEPRECATE(1) |
NAME¶
npm-deprecate - Deprecate a version of a package
Synopsis¶
npm deprecate <pkg>[@<version range>] <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:
npm deprecate my-thing@"< 0.2.3" "critical bug fixed in v0.2.3"
SemVer ranges passed to this command are interpreted such that they do include prerelease versions. For example:
npm deprecate my-thing@1.x "1.x is no longer supported"
In this case, a version my-thing@1.0.0-beta.0 will also be deprecated.
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 help publish
- npm help registry
- npm owner /cli-commands/owner
- npm owner /cli-commands/adduser
undefined NaN |