blob: 0ad7e687cf8c5d7f919455d3c1e73e4874302442 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
---
section: cli-commands
title: npm-unpublish
description: Remove a package from the registry
---
# npm-unpublish
## Remove a package from the registry
### Synopsis
```bash
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`](/docs/using-npm/scope).
### See Also
* [npm deprecate](/cli-commands/npm-deprecate)
* [npm publish](/cli-commands/npm-publish)
* [npm registry](/using-npm/registry)
* [npm adduser](/cli-commands/npm-adduser)
* [npm owner](/cli-commands/npm-owner)
|
