AndroidRemoteController/nodejs/backup/npm/man/man7/removal.7

.TH "REMOVAL" "7" "March 2026" "NPM@11.12.0" ""
.SH "NAME"
\fBRemoval\fR - Cleaning the slate
.SS "Synopsis"
.P
So sad to see you go.
.P
.RS 2
.nf
sudo npm uninstall npm -g
.fi
.RE
.P
Or, if that fails, please proceed to more severe uninstalling methods.
.SS "More Severe Uninstalling"
.P
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
Note that this is only necessary for globally-installed packages. Local installs are completely contained within a project's \fBnode_modules\fR folder. Delete that folder, and everything is gone unless a package's install script is particularly ill-behaved.
.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
To remove everything npm-related manually:
.P
.RS 2
.nf
rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/npm*
.fi
.RE
.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
.RS 2
.nf
ls -laF /usr/local/{lib/node{,/.npm},bin,share/man} | grep npm
.fi
.RE
.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
.RS 2
.nf
find /usr/local/{lib/node,bin} -exec grep -l npm \[rs]{\[rs]} \[rs]; ;
.fi
.RE
.SS "See also"
.RS 0
.IP \(bu 4
npm help uninstall
.IP \(bu 4
npm help prune
.RE 0