FM / man1

/home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1/

/home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1

Name	Size	Mode	Actions
npm-access.1	4062	0644	edit dl rm
npm-adduser.1	1992	0644	edit dl rm
npm-audit.1	17381	0644	edit dl rm
npm-bugs.1	3379	0644	edit dl rm
npm-cache.1	3132	0644	edit dl rm
npm-ci.1	10181	0644	edit dl rm
npm-completion.1	997	0644	edit dl rm
npm-config.1	4636	0644	edit dl rm
npm-dedupe.1	9862	0644	edit dl rm
npm-deprecate.1	1892	0644	edit dl rm
npm-diff.1	9771	0644	edit dl rm
npm-dist-tag.1	5636	0644	edit dl rm
npm-docs.1	3361	0644	edit dl rm
npm-doctor.1	5372	0644	edit dl rm
npm-edit.1	1180	0644	edit dl rm
npm-exec.1	12491	0644	edit dl rm
npm-explain.1	2937	0644	edit dl rm
npm-explore.1	1089	0644	edit dl rm
npm-find-dupes.1	7590	0644	edit dl rm
npm-fund.1	4054	0644	edit dl rm
npm-help-search.1	867	0644	edit dl rm
npm-help.1	1099	0644	edit dl rm
npm-hook.1	2708	0644	edit dl rm
npm-init.1	11103	0644	edit dl rm
npm-install-ci-test.1	8320	0644	edit dl rm
npm-install-test.1	11149	0644	edit dl rm
npm-install.1	26964	0644	edit dl rm
npm-link.1	12950	0644	edit dl rm
npm-login.1	2345	0644	edit dl rm
npm-logout.1	1887	0644	edit dl rm
npm-ls.1	9419	0644	edit dl rm
npm-org.1	2310	0644	edit dl rm
npm-outdated.1	6377	0644	edit dl rm
npm-owner.1	3363	0644	edit dl rm
npm-pack.1	3876	0644	edit dl rm
npm-ping.1	849	0644	edit dl rm
npm-pkg.1	8704	0644	edit dl rm
npm-prefix.1	1317	0644	edit dl rm
npm-profile.1	3421	0644	edit dl rm
npm-prune.1	6457	0644	edit dl rm
npm-publish.1	8309	0644	edit dl rm
npm-query.1	7688	0644	edit dl rm
npm-rebuild.1	5664	0644	edit dl rm
npm-repo.1	3143	0644	edit dl rm
npm-restart.1	1709	0644	edit dl rm
npm-root.1	1194	0644	edit dl rm
npm-run-script.1	8377	0644	edit dl rm
npm-sbom.1	8996	0644	edit dl rm
npm-search.1	3952	0644	edit dl rm
npm-shrinkwrap.1	1004	0644	edit dl rm
npm-star.1	1807	0644	edit dl rm
npm-stars.1	795	0644	edit dl rm
npm-start.1	1835	0644	edit dl rm
npm-stop.1	1466	0644	edit dl rm
npm-team.1	4503	0644	edit dl rm
npm-test.1	1379	0644	edit dl rm
npm-token.1	3186	0644	edit dl rm
npm-uninstall.1	4986	0644	edit dl rm
npm-unpublish.1	4900	0644	edit dl rm
npm-unstar.1	1658	0644	edit dl rm
npm-update.1	13223	0644	edit dl rm
npm-version.1	7755	0644	edit dl rm
npm-view.1	6146	0644	edit dl rm
npm-whoami.1	873	0644	edit dl rm
npm.1	5947	0644	edit dl rm
npx.1	6407	0644	edit dl rm

Edit: /home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1/npm-uninstall.1 (4986B)

.TH "NPM-UNINSTALL" "1" "July 2024" "NPM@10.8.2" ""
.SH "NAME"
\fBnpm-uninstall\fR - Remove a package
.SS "Synopsis"
.P
.RS 2
.nf
npm uninstall \[lB]<@scope>/\[rB]<pkg>...

aliases: unlink, remove, rm, r, un
.fi
.RE
.SS "Description"
.P
This uninstalls a package, completely removing everything npm installed on its behalf.
.P
It also removes the package from the \fBdependencies\fR, \fBdevDependencies\fR, \fBoptionalDependencies\fR, and \fBpeerDependencies\fR objects in your \fBpackage.json\fR.
.P
Further, if you have an \fBnpm-shrinkwrap.json\fR or \fBpackage-lock.json\fR, npm will update those files as well.
.P
\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.
.P
\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 file
.P
In 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.
.P
Scope is optional and follows the usual rules for npm help scope.
.SS "Examples"
.P
.RS 2
.nf
npm uninstall sax
.fi
.RE
.P
\fBsax\fR will no longer be in your \fBpackage.json\fR, \fBnpm-shrinkwrap.json\fR, or \fBpackage-lock.json\fR files.
.P
.RS 2
.nf
npm uninstall lodash --no-save
.fi
.RE
.P
\fBlodash\fR will not be removed from your \fBpackage.json\fR, \fBnpm-shrinkwrap.json\fR, or \fBpackage-lock.json\fR files.
.SS "Configuration"
.SS "\fBsave\fR"
.RS 0
.IP \(bu 4
Default: \fBtrue\fR unless when using \fBnpm update\fR where it defaults to \fBfalse\fR
.IP \(bu 4
Type: Boolean
.RE 0

.P
Save installed packages to a \fBpackage.json\fR file as dependencies.
.P
When used with the \fBnpm rm\fR command, removes the dependency from \fBpackage.json\fR.
.P
Will also prevent writing to \fBpackage-lock.json\fR if set to \fBfalse\fR.
.SS "\fBglobal\fR"
.RS 0
.IP \(bu 4
Default: false
.IP \(bu 4
Type: Boolean
.RE 0

.P
Operates 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.
.RS 0
.IP \(bu 4
packages are installed into the \fB{prefix}/lib/node_modules\fR folder, instead of the current working directory.
.IP \(bu 4
bin files are linked to \fB{prefix}/bin\fR
.IP \(bu 4
man pages are linked to \fB{prefix}/share/man\fR
.RE 0

.SS "\fBworkspace\fR"
.RS 0
.IP \(bu 4
Default:
.IP \(bu 4
Type: String (can be set multiple times)
.RE 0

.P
Enable 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.
.P
Valid values for the \fBworkspace\fR config are either:
.RS 0
.IP \(bu 4
Workspace names
.IP \(bu 4
Path to a workspace directory
.IP \(bu 4
Path to a parent workspace directory (will result in selecting all workspaces within that folder)
.RE 0

.P
When 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.
.P
This value is not exported to the environment for child processes.
.SS "\fBworkspaces\fR"
.RS 0
.IP \(bu 4
Default: null
.IP \(bu 4
Type: null or Boolean
.RE 0

.P
Set to true to run the command in the context of \fBall\fR configured workspaces.
.P
Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly:
.RS 0
.IP \(bu 4
Commands 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.
.RE 0

.P
This value is not exported to the environment for child processes.
.SS "\fBinclude-workspace-root\fR"
.RS 0
.IP \(bu 4
Default: false
.IP \(bu 4
Type: Boolean
.RE 0

.P
Include the workspace root when workspaces are enabled for a command.
.P
When 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.
.P
This value is not exported to the environment for child processes.
.SS "\fBinstall-links\fR"
.RS 0
.IP \(bu 4
Default: false
.IP \(bu 4
Type: Boolean
.RE 0

.P
When set file: protocol dependencies will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.
.SS "See Also"
.RS 0
.IP \(bu 4
npm help prune
.IP \(bu 4
npm help install
.IP \(bu 4
npm help folders
.IP \(bu 4
npm help config
.IP \(bu 4
npm help npmrc
.RE 0

cmd: