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

.P
To learn more about how the npm registry treats unpublish, see our <a
href="https://docs\.npmjs\.com/policies/unpublish" target="_blank"
rel="noopener noreferrer"> unpublish policies</a>
.SH Warning
.P
Consider using the \fBdeprecate\fP command instead,
.br
if your intent is to encourage users to upgrade, or if you no longer
.br
want to maintain a package\.
.SH Description
.P
This removes a package version from the registry, deleting its entry and
.br
removing the tarball\.
.P
The npm registry will return an error if you are not logged
.br
in\.
.P
If you do not specify a version or if you remove all of a package's
.br
versions then the registry will remove the root package entry entirely\.
.P
Even if you unpublish a package version, that specific name and version
.br
combination can never be reused\. In order to publish the package again,
.br
you must use a new version number\. If you unpublish the entire package,
.br
you may not publish any new versions of that package until 24 hours have
.br
passed\.
.SH Configuration
<!\-\- AUTOGENERATED CONFIG DESCRIPTIONS \-\->

.SH See Also

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

.RE