mirror of https://github.com/nodejs/node.git
28 lines
1.5 KiB
HTML
28 lines
1.5 KiB
HTML
<h1><a href="../cli/npm-unpublish.html">npm-unpublish</a></h1> <p>Remove a package from the registry</p>
|
|
<h2 id="synopsis">SYNOPSIS</h2>
|
|
<pre><code>npm unpublish [@<scope>/]<name>[@<version>]
|
|
</code></pre><h2 id="warning">WARNING</h2>
|
|
<p><strong>It is generally considered bad behavior to remove versions of a library
|
|
that others are depending on!</strong></p>
|
|
<p>Consider using the <code>deprecate</code> command
|
|
instead, if your intent is to encourage users to upgrade.</p>
|
|
<p>There is plenty of room on the registry.</p>
|
|
<h2 id="description">DESCRIPTION</h2>
|
|
<p>This removes a package version from the registry, deleting its
|
|
entry and removing the tarball.</p>
|
|
<p>If no version is specified, or if all versions are removed then
|
|
the root package entry is removed from the registry entirely.</p>
|
|
<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.</p>
|
|
<p>The scope is optional and follows the usual rules for <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>.</p>
|
|
<h2 id="see-also">SEE ALSO</h2>
|
|
<ul>
|
|
<li><a href="../cli/npm-deprecate.html">npm-deprecate(1)</a></li>
|
|
<li><a href="../cli/npm-publish.html">npm-publish(1)</a></li>
|
|
<li><a href="../misc/npm-registry.html">npm-registry(7)</a></li>
|
|
<li><a href="../cli/npm-adduser.html">npm-adduser(1)</a></li>
|
|
<li><a href="../cli/npm-owner.html">npm-owner(1)</a></li>
|
|
</ul>
|
|
|