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-explain.1 (2963B)

.TH "NPM\-EXPLAIN" "1" "February 2023" "" ""
.SH "NAME"
\fBnpm-explain\fR \- Explain installed packages
.SS Synopsis
.P
.RS 2
.nf
npm explain <package\-spec>

alias: why
.fi
.RE
.SS Description
.P
This command will print the chain of dependencies causing a given package
to be installed in the current project\.
.P
If one or more package specs are provided, then only packages matching
one of the specifiers will have their relationships explained\.
.P
The package spec can also refer to a folder within \fB\|\./node_modules\fP
.P
For example, running \fBnpm explain glob\fP within npm's source tree will show:
.P
.RS 2
.nf
glob@7\.1\.6
node_modules/glob
  glob@"^7\.1\.4" from the root project

glob@7\.1\.1 dev
node_modules/tacks/node_modules/glob
  glob@"^7\.0\.5" from rimraf@2\.6\.2
  node_modules/tacks/node_modules/rimraf
    rimraf@"^2\.6\.2" from tacks@1\.3\.0
    node_modules/tacks
      dev tacks@"^1\.3\.0" from the root project
.fi
.RE
.P
To explain just the package residing at a specific folder, pass that as the
argument to the command\.  This can be useful when trying to figure out
exactly why a given dependency is being duplicated to satisfy conflicting
version requirements within the project\.
.P
.RS 2
.nf
$ npm explain node_modules/nyc/node_modules/find\-up
find\-up@3\.0\.0 dev
node_modules/nyc/node_modules/find\-up
  find\-up@"^3\.0\.0" from nyc@14\.1\.1
  node_modules/nyc
    nyc@"^14\.1\.1" from tap@14\.10\.8
    node_modules/tap
      dev tap@"^14\.10\.8" from the root project
.fi
.RE
.SS Configuration
.SS \fBjson\fP
.RS 0
.IP \(bu 2
Default: false
.IP \(bu 2
Type: Boolean

.RE
.P
Whether or not to output JSON data, rather than the normal output\.
.RS 0
.IP \(bu 2
In \fBnpm pkg set\fP it enables parsing set values with JSON\.parse() before
saving them to your \fBpackage\.json\fP\|\.

.RE
.P
Not supported by all npm commands\.
.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 See Also
.RS 0
.IP \(bu 2
npm help "package spec"
.IP \(bu 2
npm help config
.IP \(bu 2
npm help npmrc
.IP \(bu 2
npm help folders
.IP \(bu 2
npm help ls
.IP \(bu 2
npm help install
.IP \(bu 2
npm help link
.IP \(bu 2
npm help prune
.IP \(bu 2
npm help outdated
.IP \(bu 2
npm help update

.RE

cmd: