|
|
.TH "NPM\-DEPRECATE" "1" "August 2018" "" ""
|
|
|
.SH "NAME"
|
|
|
\fBnpm-deprecate\fR \- Deprecate a version of a package
|
|
|
.SH SYNOPSIS
|
|
|
.P
|
|
|
.RS 2
|
|
|
.nf
|
|
|
npm deprecate <pkg>[@<version>] <message>
|
|
|
.fi
|
|
|
.RE
|
|
|
.SH DESCRIPTION
|
|
|
.P
|
|
|
This command will update the npm registry entry for a package, providing
|
|
|
a deprecation warning to all who attempt to install it\.
|
|
|
.P
|
|
|
It works on version ranges as well as specific versions, so you can do
|
|
|
something like this:
|
|
|
.P
|
|
|
.RS 2
|
|
|
.nf
|
|
|
npm deprecate my\-thing@"< 0\.2\.3" "critical bug fixed in v0\.2\.3"
|
|
|
.fi
|
|
|
.RE
|
|
|
.P
|
|
|
Note that you must be the package owner to deprecate something\. See the
|
|
|
\fBowner\fP and \fBadduser\fP help topics\.
|
|
|
.P
|
|
|
To un\-deprecate a package, specify an empty string (\fB""\fP) for the \fBmessage\fP argument\.
|
|
|
.SH SEE ALSO
|
|
|
.RS 0
|
|
|
.IP \(bu 2
|
|
|
npm help publish
|
|
|
.IP \(bu 2
|
|
|
npm help 7 registry
|
|
|
|
|
|
.RE
|
|
|
|