blob: e152c80b7717d5ee180437dd277f2440880c000d (
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
|
.TH "NPM\-UNPUBLISH" "1" "April 2017" "" ""
.SH "NAME"
\fBnpm-unpublish\fR \- Remove a package from the registry
.SH SYNOPSIS
.P
.RS 2
.nf
npm unpublish [<@scope>/]<pkg>[@<version>]
.fi
.RE
.SH WARNING
.P
\fBIt is generally considered bad behavior to remove versions of a library
that others are depending on!\fR
.P
Consider using the \fBdeprecate\fP command
instead, if your intent is to encourage users to upgrade\.
.P
There is plenty of room on the registry\.
.SH DESCRIPTION
.P
This removes a package version from the registry, deleting its
entry and removing the tarball\.
.P
If no version is specified, or if all versions are removed then
the root package entry is removed from the registry entirely\.
.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
With the default registry (\fBregistry\.npmjs\.org\fP), unpublish is
only allowed with versions published in the last 24 hours\. If you
are trying to unpublish a version published longer ago than that,
contact support@npmjs\.com\.
.P
The scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fP\|\.
.SH SEE ALSO
.RS 0
.IP \(bu 2
npm help deprecate
.IP \(bu 2
npm help publish
.IP \(bu 2
npm help 7 registry
.IP \(bu 2
npm help adduser
.IP \(bu 2
npm help owner
.RE
|
