FM / using-npm

/usr/local/lib/node_modules/npm/docs/content/using-npm/

/usr/local/lib/node_modules/npm/docs/content/using-npm

Name	Size	Mode	Actions
config.md	52081	0644	edit dl rm
dependency-selectors.md	12292	0644	edit dl rm
developers.md	7873	0644	edit dl rm
logging.md	3894	0644	edit dl rm
orgs.md	2268	0644	edit dl rm
package-spec.md	2874	0644	edit dl rm
registry.md	3484	0644	edit dl rm
removal.md	1645	0644	edit dl rm
scope.md	5154	0644	edit dl rm
scripts.md	14455	0644	edit dl rm
workspaces.md	6611	0644	edit dl rm

Edit: /usr/local/lib/node_modules/npm/docs/content/using-npm/removal.md (1645B)

---
title: Removal
section: 7
description: Cleaning the slate
---

### Synopsis

So sad to see you go.

```bash
sudo npm uninstall npm -g
```

Or, if that fails, please proceed to more severe uninstalling methods.

### 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.

Note that this is only necessary for globally-installed packages.
Local installs are completely contained within a project's `node_modules` folder.
Delete that folder, and everything is gone unless a package's install script is particularly ill-behaved.

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.

To remove everything npm-related manually:

```bash
rm -rf /usr/local/{lib/node{,/.npm,_modules},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:

```bash
ls -laF /usr/local/{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:

```bash
find /usr/local/{lib/node,bin} -exec grep -l npm \{\} \; ;
```

### See also

* [npm uninstall](/commands/npm-uninstall)
* [npm prune](/commands/npm-prune)

--- title: Removal section: 7 description: Cleaning the slate --- ### Synopsis So sad to see you go. ```bash sudo npm uninstall npm -g ``` Or, if that fails, please proceed to more severe uninstalling methods. ### 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. Note that this is only necessary for globally-installed packages. Local installs are completely contained within a project's `node_modules` folder. Delete that folder, and everything is gone unless a package's install script is particularly ill-behaved. 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. To remove everything npm-related manually: ```bash rm -rf /usr/local/{lib/node{,/.npm,_modules},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: ```bash ls -laF /usr/local/{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: ```bash find /usr/local/{lib/node,bin} -exec grep -l npm \{\} \; ; ``` ### See also * [npm uninstall](/commands/npm-uninstall) * [npm prune](/commands/npm-prune)