| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748 |
- .TH "NPM\-UNPUBLISH" "1" "August 2021" "" ""
- .SH "NAME"
- \fBnpm-unpublish\fR \- Remove a package from the registry
- .SS Synopsis
- .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 \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
- If no version is specified, or if all versions are removed then
- the root package entry is removed from the registry entirely\.
- .P
- Even if a package version is unpublished, that specific name and
- version combination can never be reused\. In order to publish the
- package again, a new version number must be used\. If you unpublish the entire package, you may not publish any new versions of that package until 24 hours have passed\.
- .P
- To learn more about how unpublish is treated on the npm registry, see our <a href="https://www\.npmjs\.com/policies/unpublish" target="_blank" rel="noopener noreferrer"> unpublish policies</a>\|\.
- .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
- .RE
|
