.TH "NPM\-DEPRECATE" "1" "November 2022" "9.1.1"
.SH "NAME"
\fBnpm-deprecate\fR
.SH Synopsis
<!\-\- AUTOGENERATED USAGE DESCRIPTIONS \-\->

.P
Note: This command is unaware of workspaces\.
.SH Description
.P
This command will update the npm registry entry for a package, providing a
.br
deprecation warning to all who attempt to install it\.
.P
It works on version ranges as well as specific
.br
versions, so you can do something like this:
.RS 2
.nf
npm deprecate my\-thing@"< 0\.2\.3" "critical bug fixed in v0\.2\.3"
.fi
.RE
.P
SemVer ranges passed to this command are interpreted such that they \fIdo\fR
.br
include prerelease versions\.  For example:
.RS 2
.nf
npm deprecate my\-thing@1\.x "1\.x is no longer supported"
.fi
.RE
.P
In this case, a version \fBmy\-thing@1\.0\.0\-beta\.0\fP will also be deprecated\.
.P
You must be the package owner to deprecate something\.  See the \fBowner\fP and
.br
\fBadduser\fP help topics\.
.P
To un\-deprecate a package, specify an empty string (\fB&quot;&quot;\fP) for the \fBmessage\fP
.br
argument\. Note that you must use double quotes with no space between them to
.br
format an empty string\.
.SH Configuration
<!\-\- AUTOGENERATED CONFIG DESCRIPTIONS \-\->

.SH See Also

.RS 1
.IP \(bu 2
package spec
.IP \(bu 2
npm publish
.IP \(bu 2
npm registry
.IP \(bu 2
npm owner
.IP \(bu 2
npm adduser

.RE