/var/lang/lib/node_modules/npm/man/man7
This explorer reads the filesystem of the server it runs on, so /workspace/user isn't present here. Browsing and the terminal still work against this server's own disk from /.
.TH "REMOVAL" "7" "February 2026" "NPM@11.11.0" "".SH "NAME"\fBRemoval\fR - Cleaning the slate.SS "Synopsis".PSo sad to see you go..P.RS 2.nfsudo npm uninstall npm -g.fi.RE.POr, if that fails, please proceed to more severe uninstalling methods..SS "More Severe Uninstalling".PUsually, the above instructions are sufficient. That will remove npm, but leave behind anything you've installed..PIf that doesn't work, or if you require more drastic measures, continue reading..PNote 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..PThis 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..PTo remove everything npm-related manually:.P.RS 2.nfrm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/npm*.fi.RE.PIf 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.nfls -laF /usr/local/{lib/node{,/.npm},bin,share/man} | grep npm.fi.RE.PPrior 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.nffind /usr/local/{lib/node,bin} -exec grep -l npm \[rs]{\[rs]} \[rs]; ;.fi.RE.SS "See also".RS 0.IP \(bu 4npm help uninstall.IP \(bu 4npm help prune.RE 0