.TH "NPM\-UNPUBLISH" "1" "undefined NaN" "" ""
.SH "NAME"
\fBnpm-unpublish\fR \- Remove a package from the registry
.SS Synopsis
.P
To learn more about how the npm registry treats unpublish, see our <a
href="https://www\.npmjs\.com/policies/unpublish" target="_blank"
rel="noopener noreferrer"> unpublish policies</a>
.SS Unpublishing a single version of a package
.P
.RS 2
.nf
npm unpublish [<@scope>/]<pkg>@<version>
.fi
.RE
.SS Unpublishing an entire package
.P
.RS 2
.nf
npm unpublish [<@scope>/]<pkg> \-\-force
.fi
.RE
.SS Warning
.P
Consider using the npm help \fBdeprecate\fP command instead,
if your intent is to encourage users to upgrade, or if you no longer
want to maintain a package\.
.SS Description
.P
This removes a package version from the registry, deleting its entry and
removing the tarball\.
.P
The npm registry will return an error if you are not npm help logged
in\.
.P
If you do not specify a version or if you remove all of a package's
versions then the registry will remove the root package entry entirely\.
.P
Even if you unpublish a package version, that specific name and version
combination can never be reused\. In order to publish the package again,
you must use a new version number\. If you unpublish the entire package,
you may not publish any new versions of that package until 24 hours have
passed\.
.SS See Also
.RS 0
.IP \(bu 2
npm help deprecate
.IP \(bu 2
npm help publish
.IP \(bu 2
npm help registry
.IP \(bu 2
npm help adduser
.IP \(bu 2
npm help owner
.IP \(bu 2
npm help login

.RE