summaryrefslogtreecommitdiff
path: root/deps/npm/man/man1/npm-unpublish.1
blob: d6356dcc310753e509eacbec797701e4f78b8d6c (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
55
56
57
58
.\" Generated with Ronnjs 0.3.8
.\" http://github.com/kapouer/ronnjs/
.
.TH "NPM\-UNPUBLISH" "1" "April 2014" "" ""
.
.SH "NAME"
\fBnpm-unpublish\fR \-\- Remove a package from the registry
.
.SH "SYNOPSIS"
.
.nf
npm unpublish <name>[@<version>]
.
.fi
.
.SH "WARNING"
\fBIt is generally considered bad behavior to remove versions of a library
that others are depending on!\fR
.
.P
Consider using the \fBdeprecate\fR command
instead, if your intent is to encourage users to upgrade\.
.
.P
There is plenty of room on the registry\.
.
.SH "DESCRIPTION"
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\.
.
.SH "SEE ALSO"
.
.IP "\(bu" 4
npm help deprecate
.
.IP "\(bu" 4
npm help publish
.
.IP "\(bu" 4
npm help  registry
.
.IP "\(bu" 4
npm help adduser
.
.IP "\(bu" 4
npm help owner
.
.IP "" 0