Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/npm/cli.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorisaacs <i@izs.me>2011-04-24 00:19:05 +0400
committerisaacs <i@izs.me>2011-04-24 00:19:05 +0400
commitc7dee39637f59b1f0e6cb954ba1e6722ca6d16fc (patch)
tree9070bb8eb596a5760f3b647f67e049544fa15c9e /README.md
parent21f17714c0955354c345d080f6d5ac43baadba48 (diff)
Add npm removal instructions
Diffstat (limited to 'README.md')
-rw-r--r--README.md27
1 files changed, 27 insertions, 0 deletions
diff --git a/README.md b/README.md
index dc8573b5c..8e224e33d 100644
--- a/README.md
+++ b/README.md
@@ -128,6 +128,33 @@ Or, if that fails,
sudo make uninstall
+## More Severe Uninstalling
+
+Usually, the above instructions are sufficient. That will remove
+npm, but leave behind anything you've installed.
+
+If that doesn't work, or if you require more drastic measures,
+continue reading.
+
+This assumes that you installed node and npm in the default place. If
+you configured node with a different `--prefix`, or installed npm with a
+different prefix setting, then adjust the paths accordingly, replacing
+`/usr/local` with your install prefix.
+
+ rm -rf /usr/local/{lib/node,lib/node/.npm,bin,share/man}/npm*
+
+If you installed things *with* 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:
+
+ ls -laF /usr/local/{lib/node,lib/node/.npm,bin,share/man} | grep npm
+
+Prior to version 0.3, npm used shim files for executables and node
+modules. To track those down, you can do the following:
+
+ find /usr/local/{lib/node,bin} -exec grep -l npm \{\} \; ;
+
## Using npm Programmatically
If you would like to use npm programmatically, you can do that as of