GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
NPM-UNPUBLISH(1) NPM-UNPUBLISH(1)

npm-unpublish - Remove a package from the registry

npm unpublish [<@scope>/]<pkg>[@<version>]

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.

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 .
The scope is optional and follows the usual rules for npm help 7 npm-scope.

npm help deprecate
npm help publish
npm help 7 registry
npm help adduser
npm help owner
August 2018

Search for    or go to Top of page |  Section 1 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.