.TH "NPM\-UNINSTALL" "1" "November 2022" "9.1.1"
.SH "NAME"
\fBnpm-uninstall\fR
.SH Synopsis
<!\-\- AUTOGENERATED USAGE DESCRIPTIONS \-\->

.SH Description
.P
This uninstalls a package, completely removing everything npm installed
.br
on its behalf\.
.P
It also removes the package from the \fBdependencies\fP, \fBdevDependencies\fP,
.br
\fBoptionalDependencies\fP, and \fBpeerDependencies\fP objects in your
.br
\fBpackage\.json\fP\|\.
.P
Further, if you have an \fBnpm\-shrinkwrap\.json\fP or \fBpackage\-lock\.json\fP, npm
.br
will update those files as well\.
.P
\fB\-\-no\-save\fP will tell npm not to remove the package from your
.br
\fBpackage\.json\fP, \fBnpm\-shrinkwrap\.json\fP, or \fBpackage\-lock\.json\fP files\.
.P
\fB\-\-save\fP or \fB\-S\fP will tell npm to remove the package from your
.br
\fBpackage\.json\fP, \fBnpm\-shrinkwrap\.json\fP, and \fBpackage\-lock\.json\fP files\.
.br
This is the default, but you may need to use this if you have for
.br
instance \fBsave=false\fP in your \fBnpmrc\fP file
.P
In global mode (ie, with \fB\-g\fP or \fB\-\-global\fP appended to the command),
.br
it uninstalls the current package context as a global package\.
.br
\fB\-\-no\-save\fP is ignored in this case\.
.P
Scope is optional and follows the usual rules for \fBscope\fP\|\.
.SH Examples
.RS 2
.nf
npm uninstall sax
.fi
.RE
.P
\fBsax\fP will no longer be in your \fBpackage\.json\fP, \fBnpm\-shrinkwrap\.json\fP, or
.br
\fBpackage\-lock\.json\fP files\.
.RS 2
.nf
npm uninstall lodash \-\-no\-save
.fi
.RE
.P
\fBlodash\fP will not be removed from your \fBpackage\.json\fP,
.br
\fBnpm\-shrinkwrap\.json\fP, or \fBpackage\-lock\.json\fP files\.
.SH Configuration
<!\-\- AUTOGENERATED CONFIG DESCRIPTIONS \-\->

.SH See Also

.RS 1
.IP \(bu 2
npm prune
.IP \(bu 2
npm install
.IP \(bu 2
npm folders
.IP \(bu 2
npm config
.IP \(bu 2
npmrc

.RE