npm-explainExplain installed packages
npm explain <folder | specifier>alias: why
This command will print the chain of dependencies causing a given package to be installed in the current project.
Positional arguments can be either folders within
name@version-range specifiers, which will select the dependency
relationships to explain.
For example, running
npm explain glob within npm's source tree will show:
firstname.lastname@example.org_modules/globglob@"^7.1.4" from the root email@example.com devnode_modules/tacks/node_modules/globglob@"^7.0.5" from firstname.lastname@example.org_modules/tacks/node_modules/rimrafrimraf@"^2.6.2" from email@example.com_modules/tacksdev tacks@"^1.3.0" from the root project
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.
$ npm explain firstname.lastname@example.org devnode_modules/nyc/node_modules/find-upfind-up@"^3.0.0" from email@example.com_modules/nycnyc@"^14.1.1" from firstname.lastname@example.org_modules/tapdev tap@"^14.10.8" from the root project
- Default: false
- Type: Boolean
Whether or not to output JSON data, rather than the normal output.
npm pkg setit enables parsing set values with JSON.parse() before saving them to your
Not supported by all npm commands.
- Type: String (can be set multiple times)
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.
Valid values for the
workspace config are either:
- Workspace names
- Path to a workspace directory
- Path to a parent workspace directory (will result to selecting all of the nested workspaces)
When set for the
npm init 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.
This value is not exported to the environment for child processes.