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
59
60
61
62
63
64
65
66
|
.\" Generated with Ronnjs/v0.1
.\" http://github.com/kapouer/ronnjs/
.
.TH "NPM\-REMOVAL" "1" "May 2011" "" ""
.
.SH "NAME"
\fBnpm-removal\fR \-\- Cleaning the Slate
.
.SH "SUMMARY"
So sad to see you go\.
.
.IP "" 4
.
.nf
sudo npm uninstall npm \-g
.
.fi
.
.IP "" 0
.
.P
Or, if that fails, get the npm source code, and do:
.
.IP "" 4
.
.nf
sudo make uninstall
.
.fi
.
.IP "" 0
.
.SH "More Severe Uninstalling"
Usually, the above instructions are sufficient\. That will remove
npm, but leave behind anything you\'ve installed\.
.
.P
If that doesn\'t work, or if you require more drastic measures,
continue reading\.
.
.P
This assumes that you installed node and npm in the default place\. If
you configured node with a different \fB\-\-prefix\fR, or installed npm with a
different prefix setting, then adjust the paths accordingly, replacing \fB/usr/local\fR with your install prefix\.
.
.P
rm \-rf /usr/local/{lib/node,lib/node/\.npm,bin,share/man}/npm*
.
.P
If you installed things \fIwith\fR npm, then your best bet is to uninstall
them with npm first, and then install them again once you have a
proper install\. This can help find any symlinks that are lying
around:
.
.P
ls \-laF /usr/local/{lib/node,lib/node/\.npm,bin,share/man} | grep npm
.
.P
Prior to version 0\.3, npm used shim files for executables and node
modules\. To track those down, you can do the following:
.
.P
find /usr/local/{lib/node,bin} \-exec grep \-l npm {} \\; ;
.
.P
(This is also in the README file\.)
|
