npm-find-dupes - Find duplication in the package tree
npm find-dupes
Runs npm dedupe in --dry-run mode, making npm only output the duplications, without actually changing the package tree.
|
• |
Default: "hoisted" |
|||
|
• |
Type: "hoisted", "nested", "shallow", or "linked" |
Sets the strategy for installing packages in node_modules. hoisted (default): Install non-duplicated in top-level, and duplicated as necessary within directory structure. nested: (formerly --legacy-bundling) install in place, no hoisting. shallow (formerly --global-style) only install direct deps at top-level. linked: (experimental) install in node_modules/.store, link in place, unhoisted.
|
• |
Default: false | ||
|
• |
Type: Boolean | ||
|
• |
DEPRECATED: This option has been deprecated in favor of --install-strategy=nested |
Instead of hoisting package installs in node_modules, install packages in the same manner that they are depended on. This may cause very deep directory structures and duplicate package installs as there is no de-duplicating. Sets --install-strategy=nested.
|
• |
Default: false | ||
|
• |
Type: Boolean | ||
|
• |
DEPRECATED: This option has been deprecated in favor of --install-strategy=shallow |
Only install direct dependencies in the top level node_modules, but hoist on deeper dependencies. Sets --install-strategy=shallow.
|
• |
Default: false |
|||
|
• |
Type: Boolean |
If set to true, and --legacy-peer-deps is not set, then any conflicting peerDependencies will be treated as an install failure, even if npm could reasonably guess the appropriate resolution based on non-peer dependency relationships.
By default, conflicting peerDependencies deep in the dependency graph will be resolved using the nearest non-peer dependency specification, even if doing so will result in some packages receiving a peer dependency outside the range set in their package’s peerDependencies object.
When such an override is performed, a warning is printed, explaining the conflict and the packages involved. If --strict-peer-deps is set, then this warning is treated as a failure.
|
• |
Default: true |
|||
|
• |
Type: Boolean |
If set to false, then ignore package-lock.json files when installing. This will also prevent writing package-lock.json if save is true.
|
• |
Default: ’dev’ if the NODE_ENV environment variable is set to ’production’, otherwise empty. | ||
|
• |
Type: "dev", "optional", or "peer" (can be set multiple times) |
Dependency types to omit from the installation tree on disk.
Note that these dependencies are still resolved and added to the package-lock.json or npm-shrinkwrap.json file. They are just not physically installed on disk.
If a package type appears in both the --include and --omit lists, then it will be included.
If the resulting omit list includes ’dev’, then the NODE_ENV environment variable will be set to ’production’ for all lifecycle scripts.
|
• |
Default: | ||
|
• |
Type: "prod", "dev", "optional", or "peer" (can be set multiple times) |
Option that allows for defining which types of dependencies to install.
This is the inverse of --omit=<type>.
Dependency types specified in --include will not be omitted, regardless of the order in which omit/include are specified on the command-line.
|
• |
Default: false |
|||
|
• |
Type: Boolean |
If true, npm does not run scripts specified in package.json files.
Note that commands explicitly intended to run a particular script, such as npm start, npm stop, npm restart, npm test, and npm run-script will still run their intended script if ignore-scripts is set, but they will not run any pre- or post-scripts.
|
• |
Default: true |
|||
|
• |
Type: Boolean |
When "true" submit audit reports alongside the current npm command to the default registry and all registries configured for scopes. See the documentation for npm help audit for details on what is submitted.
|
• |
Default: true |
|||
|
• |
Type: Boolean |
Tells npm to create symlinks (or .cmd shims on Windows) for package executables.
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.
|
• |
Default: true |
|||
|
• |
Type: Boolean |
When "true" displays the message at the end of each npm install acknowledging the number of dependencies looking for funding. See npm help fund for details.
|
• |
Default: |
|||
|
• |
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 in selecting all workspaces within that folder) |
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.
|
• |
Default: null |
|||
|
• |
Type: null or Boolean |
Set to true to run the command in the context of all configured workspaces.
Explicitly setting this to false will cause commands like install to ignore workspaces altogether. When not set explicitly:
|
• |
Commands that operate on the node_modules tree (install, update, etc.) will link workspaces into the node_modules folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, unless one or more workspaces are specified in the workspace config. |
This value is not exported to the environment for child processes.
|
• |
Default: false |
|||
|
• |
Type: Boolean |
Include the workspace root when workspaces are enabled for a command.
When false, specifying individual workspaces via the workspace config, or all workspaces via the workspaces flag, will cause npm to operate only on the specified workspaces, and not on the root project.
This value is not exported to the environment for child processes.
|
• |
Default: false |
|||
|
• |
Type: Boolean |
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.
|
• |
npm help dedupe |
|||
|
• |
npm help ls |
|||
|
• |
npm help update |
|||
|
• |
npm help install |