File Explorer

1.TH "NPM-UNINSTALL" "1" "February 2026" "NPM@11.11.0" ""2.SH "NAME"3\fBnpm-uninstall\fR - Remove a package4.SS "Synopsis"5.P6.RS 27.nf8npm uninstall \[lB]<@scope>/\[rB]<pkg>...9 10aliases: unlink, remove, rm, r, un11.fi12.RE13.SS "Description"14.P15This uninstalls a package, completely removing everything npm installed on its behalf.16.P17It also removes the package from the \fBdependencies\fR, \fBdevDependencies\fR, \fBoptionalDependencies\fR, and \fBpeerDependencies\fR objects in your \fBpackage.json\fR.18.P19Further, if you have an \fBnpm-shrinkwrap.json\fR or \fBpackage-lock.json\fR, npm will update those files as well.20.P21\fB--no-save\fR will tell npm not to remove the package from your \fBpackage.json\fR, \fBnpm-shrinkwrap.json\fR, or \fBpackage-lock.json\fR files.22.P23\fB--save\fR or \fB-S\fR will tell npm to remove the package from your \fBpackage.json\fR, \fBnpm-shrinkwrap.json\fR, and \fBpackage-lock.json\fR files. This is the default, but you may need to use this if you have for instance \fBsave=false\fR in your \fBnpmrc\fR file24.P25In global mode (ie, with \fB-g\fR or \fB--global\fR appended to the command), it uninstalls the current package context as a global package. \fB--no-save\fR is ignored in this case.26.P27Scope is optional and follows the usual rules for npm help scope.28.SS "Examples"29.P30.RS 231.nf32npm uninstall sax33.fi34.RE35.P36\fBsax\fR will no longer be in your \fBpackage.json\fR, \fBnpm-shrinkwrap.json\fR, or \fBpackage-lock.json\fR files.37.P38.RS 239.nf40npm uninstall lodash --no-save41.fi42.RE43.P44\fBlodash\fR will not be removed from your \fBpackage.json\fR, \fBnpm-shrinkwrap.json\fR, or \fBpackage-lock.json\fR files.45.SS "Configuration"46.SS "\fBsave\fR"47.RS 048.IP \(bu 449Default: \fBtrue\fR unless when using \fBnpm update\fR where it defaults to \fBfalse\fR50.IP \(bu 451Type: Boolean52.RE 053 54.P55Save installed packages to a \fBpackage.json\fR file as dependencies.56.P57When used with the \fBnpm rm\fR command, removes the dependency from \fBpackage.json\fR.58.P59Will also prevent writing to \fBpackage-lock.json\fR if set to \fBfalse\fR.60.SS "\fBglobal\fR"61.RS 062.IP \(bu 463Default: false64.IP \(bu 465Type: Boolean66.RE 067 68.P69Operates in "global" mode, so that packages are installed into the \fBprefix\fR folder instead of the current working directory. See npm help folders for more on the differences in behavior.70.RS 071.IP \(bu 472packages are installed into the \fB{prefix}/lib/node_modules\fR folder, instead of the current working directory.73.IP \(bu 474bin files are linked to \fB{prefix}/bin\fR75.IP \(bu 476man pages are linked to \fB{prefix}/share/man\fR77.RE 078 79.SS "\fBworkspace\fR"80.RS 081.IP \(bu 482Default:83.IP \(bu 484Type: String (can be set multiple times)85.RE 086 87.P88Enable running a command in the context of the configured workspaces of the current project while filtering by running only the workspaces defined by this configuration option.89.P90Valid values for the \fBworkspace\fR config are either:91.RS 092.IP \(bu 493Workspace names94.IP \(bu 495Path to a workspace directory96.IP \(bu 497Path to a parent workspace directory (will result in selecting all workspaces within that folder)98.RE 099 100.P101When set for the \fBnpm init\fR command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.102.P103This value is not exported to the environment for child processes.104.SS "\fBworkspaces\fR"105.RS 0106.IP \(bu 4107Default: null108.IP \(bu 4109Type: null or Boolean110.RE 0111 112.P113Set to true to run the command in the context of \fBall\fR configured workspaces.114.P115Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly:116.RS 0117.IP \(bu 4118Commands that operate on the \fBnode_modules\fR tree (install, update, etc.) will link workspaces into the \fBnode_modules\fR folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, \fIunless\fR one or more workspaces are specified in the \fBworkspace\fR config.119.RE 0120 121.P122This value is not exported to the environment for child processes.123.SS "\fBinclude-workspace-root\fR"124.RS 0125.IP \(bu 4126Default: false127.IP \(bu 4128Type: Boolean129.RE 0130 131.P132Include the workspace root when workspaces are enabled for a command.133.P134When false, specifying individual workspaces via the \fBworkspace\fR config, or all workspaces via the \fBworkspaces\fR flag, will cause npm to operate only on the specified workspaces, and not on the root project.135.P136This value is not exported to the environment for child processes.137.SS "\fBinstall-links\fR"138.RS 0139.IP \(bu 4140Default: false141.IP \(bu 4142Type: Boolean143.RE 0144 145.P146When set file: protocol dependencies will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.147.SS "See Also"148.RS 0149.IP \(bu 4150npm help prune151.IP \(bu 4152npm help install153.IP \(bu 4154npm help folders155.IP \(bu 4156npm help config157.IP \(bu 4158npm help npmrc159.RE 0160