mirror of
https://github.com/titanscouting/tra-analysis.git
synced 2024-11-13 06:36:17 +00:00
46 lines
1.3 KiB
Markdown
46 lines
1.3 KiB
Markdown
|
npm-unpublish(1) -- Remove a package from the registry
|
||
|
|
======================================================
|
||
|
|
|
||
|
|
## SYNOPSIS
|
||
|
|
|
||
|
|
npm unpublish [<@scope>/]<pkg>[@<version>]
|
||
|
|
|
||
|
|
## WARNING
|
||
|
|
|
||
|
|
**It is generally considered bad behavior to remove versions of a library
|
||
|
|
that others are depending on!**
|
||
|
|
|
||
|
|
Consider using the `deprecate` command
|
||
|
|
instead, if your intent is to encourage users to upgrade.
|
||
|
|
|
||
|
|
There is plenty of room on the registry.
|
||
|
|
|
||
|
|
## DESCRIPTION
|
||
|
|
|
||
|
|
This removes a package version from the registry, deleting its
|
||
|
|
entry and removing the tarball.
|
||
|
|
|
||
|
|
If no version is specified, or if all versions are removed then
|
||
|
|
the root package entry is removed from the registry entirely.
|
||
|
|
|
||
|
|
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. Additionally,
|
||
|
|
new versions of packages with every version unpublished may not
|
||
|
|
be republished until 24 hours have passed.
|
||
|
|
|
||
|
|
With the default registry (`registry.npmjs.org`), unpublish is
|
||
|
|
only allowed with versions published in the last 72 hours. If you
|
||
|
|
are trying to unpublish a version published longer ago than that,
|
||
|
|
contact support@npmjs.com.
|
||
|
|
|
||
|
|
The scope is optional and follows the usual rules for `npm-scope(7)`.
|
||
|
|
|
||
|
|
## SEE ALSO
|
||
|
|
|
||
|
|
* npm-deprecate(1)
|
||
|
|
* npm-publish(1)
|
||
|
|
* npm-registry(7)
|
||
|
|
* npm-adduser(1)
|
||
|
|
* npm-owner(1)
|