1NPM-UNPUBLISH(1) NPM-UNPUBLISH(1)
2
3
4
6 npm-unpublish - Remove a package from the registry
7
9 npm unpublish [<@scope>/]<pkg>[@<version>]
10
12 It is generally considered bad behavior to remove versions of a library
13 that others are depending on!
14
15 Consider using the deprecate command instead, if your intent is to
16 encourage users to upgrade.
17
18 There is plenty of room on the registry.
19
21 This removes a package version from the registry, deleting its entry
22 and removing the tarball.
23
24 If no version is specified, or if all versions are removed then the
25 root package entry is removed from the registry entirely.
26
27 Even if a package version is unpublished, that specific name and ver‐
28 sion combination can never be reused. In order to publish the package
29 again, a new version number must be used. Additionally, new versions of
30 packages with every version unpublished may not be republished until 24
31 hours have passed.
32
33 With the default registry (registry.npmjs.org), unpublish is only
34 allowed with versions published in the last 72 hours. If you are trying
35 to unpublish a version published longer ago than that, contact sup‐
36 port@npmjs.com.
37
38 The scope is optional and follows the usual rules for npm help 7
39 npm-scope.
40
42 · npm help deprecate
43
44 · npm help publish
45
46 · npm help 7 registry
47
48 · npm help adduser
49
50 · npm help owner
51
52
53
54
55
56 October 2019 NPM-UNPUBLISH(1)