FM / man1

/home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/man/man1/

/home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/man/man1

Name	Size	Mode	Actions
npm-access.1	3647	0644	edit dl rm
npm-adduser.1	2486	0644	edit dl rm
npm-audit.1	15987	0644	edit dl rm
npm-bin.1	957	0644	edit dl rm
npm-bugs.1	3300	0644	edit dl rm
npm-cache.1	3139	0644	edit dl rm
npm-ci.1	10760	0644	edit dl rm
npm-completion.1	1001	0644	edit dl rm
npm-config.1	4176	0644	edit dl rm
npm-dedupe.1	9181	0644	edit dl rm
npm-deprecate.1	1895	0644	edit dl rm
npm-diff.1	9867	0644	edit dl rm
npm-dist-tag.1	5532	0644	edit dl rm
npm-docs.1	3283	0644	edit dl rm
npm-doctor.1	5052	0644	edit dl rm
npm-edit.1	1140	0644	edit dl rm
npm-exec.1	12396	0644	edit dl rm
npm-explain.1	2963	0644	edit dl rm
npm-explore.1	1075	0644	edit dl rm
npm-find-dupes.1	6828	0644	edit dl rm
npm-fund.1	3992	0644	edit dl rm
npm-help-search.1	865	0644	edit dl rm
npm-help.1	1075	0644	edit dl rm
npm-hook.1	2691	0644	edit dl rm
npm-init.1	10165	0644	edit dl rm
npm-install-ci-test.1	8845	0644	edit dl rm
npm-install-test.1	8921	0644	edit dl rm
npm-install.1	24814	0644	edit dl rm
npm-link.1	12253	0644	edit dl rm
npm-logout.1	1895	0644	edit dl rm
npm-ls.1	9099	0644	edit dl rm
npm-org.1	2286	0644	edit dl rm
npm-outdated.1	6445	0644	edit dl rm
npm-owner.1	3392	0644	edit dl rm
npm-pack.1	3861	0644	edit dl rm
npm-ping.1	844	0644	edit dl rm
npm-pkg.1	8354	0644	edit dl rm
npm-prefix.1	1325	0644	edit dl rm
npm-profile.1	4707	0644	edit dl rm
npm-prune.1	6114	0644	edit dl rm
npm-publish.1	7937	0644	edit dl rm
npm-query.1	5480	0644	edit dl rm
npm-rebuild.1	4801	0644	edit dl rm
npm-repo.1	3075	0644	edit dl rm
npm-restart.1	1698	0644	edit dl rm
npm-root.1	1159	0644	edit dl rm
npm-run-script.1	8159	0644	edit dl rm
npm-search.1	3926	0644	edit dl rm
npm-set-script.1	2679	0644	edit dl rm
npm-shrinkwrap.1	977	0644	edit dl rm
npm-star.1	1793	0644	edit dl rm
npm-stars.1	776	0644	edit dl rm
npm-start.1	1827	0644	edit dl rm
npm-stop.1	1457	0644	edit dl rm
npm-team.1	4422	0644	edit dl rm
npm-test.1	1369	0644	edit dl rm
npm-token.1	5264	0644	edit dl rm
npm-uninstall.1	4534	0644	edit dl rm
npm-unpublish.1	4769	0644	edit dl rm
npm-unstar.1	1639	0644	edit dl rm
npm-update.1	12495	0644	edit dl rm
npm-version.1	7708	0644	edit dl rm
npm-view.1	5749	0644	edit dl rm
npm-whoami.1	866	0644	edit dl rm
npm.1	5804	0644	edit dl rm
npx.1	6313	0644	edit dl rm

Edit: /home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/man/man1/npm-rebuild.1 (4801B)

.TH "NPM\-REBUILD" "1" "February 2023" "" ""
.SH "NAME"
\fBnpm-rebuild\fR \- Rebuild a package
.SS Synopsis
.P
.RS 2
.nf
npm rebuild [<package\-spec>] \.\.\.]

alias: rb
.fi
.RE
.SS Description
.P
This command runs the \fBnpm build\fP command on the matched folders\.  This is
useful when you install a new version of node, and must recompile all your
C++ addons with the new binary\.  It is also useful when installing with
\fB\-\-ignore\-scripts\fP and \fB\-\-no\-bin\-links\fP, to explicitly choose which
packages to build and/or link bins\.
.P
If one or more package specs are provided, then only packages with a
name and version matching one of the specifiers will be rebuilt\.
.SS Configuration
.SS \fBglobal\fP
.RS 0
.IP \(bu 2
Default: false
.IP \(bu 2
Type: Boolean

.RE
.P
Operates in "global" mode, so that packages are installed into the \fBprefix\fP
folder instead of the current working directory\. See
npm help folders for more on the differences in behavior\.
.RS 0
.IP \(bu 2
packages are installed into the \fB{prefix}/lib/node_modules\fP folder, instead
of the current working directory\.
.IP \(bu 2
bin files are linked to \fB{prefix}/bin\fP
.IP \(bu 2
man pages are linked to \fB{prefix}/share/man\fP

.RE
.SS \fBbin\-links\fP
.RS 0
.IP \(bu 2
Default: true
.IP \(bu 2
Type: Boolean

.RE
.P
Tells npm to create symlinks (or \fB\|\.cmd\fP shims on Windows) for package
executables\.
.P
Set to false to have it not do this\. This can be used to work around the
fact that some file systems don't support symlinks, even on ostensibly Unix
systems\.
.SS \fBforeground\-scripts\fP
.RS 0
.IP \(bu 2
Default: false
.IP \(bu 2
Type: Boolean

.RE
.P
Run all build scripts (ie, \fBpreinstall\fP, \fBinstall\fP, and \fBpostinstall\fP)
scripts for installed packages in the foreground process, sharing standard
input, output, and error with the main npm process\.
.P
Note that this will generally make installs run slower, and be much noisier,
but can be useful for debugging\.
.SS \fBignore\-scripts\fP
.RS 0
.IP \(bu 2
Default: false
.IP \(bu 2
Type: Boolean

.RE
.P
If true, npm does not run scripts specified in package\.json files\.
.P
Note that commands explicitly intended to run a particular script, such as
\fBnpm start\fP, \fBnpm stop\fP, \fBnpm restart\fP, \fBnpm test\fP, and \fBnpm run\-script\fP
will still run their intended script if \fBignore\-scripts\fP is set, but they
will \fInot\fR run any pre\- or post\-scripts\.
.SS \fBworkspace\fP
.RS 0
.IP \(bu 2
Default:
.IP \(bu 2
Type: String (can be set multiple times)

.RE
.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\fP config are either:
.RS 0
.IP \(bu 2
Workspace names
.IP \(bu 2
Path to a workspace directory
.IP \(bu 2
Path to a parent workspace directory (will result in selecting all
workspaces within that folder)

.RE
.P
When set for the \fBnpm init\fP 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\fP
.RS 0
.IP \(bu 2
Default: null
.IP \(bu 2
Type: null or Boolean

.RE
.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\fP to
ignore workspaces altogether\. When not set explicitly:
.RS 0
.IP \(bu 2
Commands that operate on the \fBnode_modules\fP tree (install, update, etc\.)
will link workspaces into the \fBnode_modules\fP 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\fP config\.

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

.RE
.P
Include the workspace root when workspaces are enabled for a command\.
.P
When false, specifying individual workspaces via the \fBworkspace\fP config, or
all workspaces via the \fBworkspaces\fP 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\fP
.RS 0
.IP \(bu 2
Default: false
.IP \(bu 2
Type: Boolean

.RE
.P
When set file: protocol dependencies that exist outside of the project root
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 2
npm help "package spec"
.IP \(bu 2
npm help install

.RE

cmd: