From c7dee39637f59b1f0e6cb954ba1e6722ca6d16fc Mon Sep 17 00:00:00 2001 From: isaacs Date: Sat, 23 Apr 2011 13:19:05 -0700 Subject: Add npm removal instructions --- doc/removing-npm.md | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 doc/removing-npm.md (limited to 'doc') diff --git a/doc/removing-npm.md b/doc/removing-npm.md new file mode 100644 index 000000000..b13509686 --- /dev/null +++ b/doc/removing-npm.md @@ -0,0 +1,39 @@ +npm-removal(1) -- Cleaning the Slate +==================================== + +So sad to see you go. + + sudo npm uninstall npm -g + +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 \{\} \; ; + +(This is also in the README file.) -- cgit v1.2.3