dhei/classic-tokens
@reggi/path-to-regexp
dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2
dependabot/npm_and_yarn/main/eslint-10.4.0
dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0
dependabot/npm_and_yarn/main/proc-log-7.0.0
dependabot/npm_and_yarn/npm_and_yarn-826852524d
dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2
deprecate-totp-2fa
dhei/classic-tokens
gat-bypass-2fa-docs
jpg619/fix-accessibility-content-flow
jpg619/version-bump-tar-2
kartykp/gat-bypass-2fa-docs
kartykp/upgrade-path-to-regex
main
maitxn/version-bump-tar
patch-1
reggi/cache-based-on-version
reggi/dev-engines
reggi/fix-transform-prettier
reggi/overrides
update-search-sensitivity
| 1 | --- |
| 2 | title: npm-find-dupes |
| 3 | section: 1 |
| 4 | description: Find duplication in the package tree |
| 5 | github_repo: npm/cli |
| 6 | github_branch: release/v10 |
| 7 | github_path: docs/lib/content/commands/npm-find-dupes.md |
| 8 | redirect_from: |
| 9 | - /cli-documentation/v10/cli-commands/find-dupes |
| 10 | - /cli-documentation/v10/cli-commands/npm-find-dupes |
| 11 | - /cli-documentation/v10/commands/find-dupes |
| 12 | - /cli-documentation/v10/commands/npm-find-dupes |
| 13 | - /cli-documentation/v10/find-dupes |
| 14 | - /cli-documentation/v10/npm-find-dupes |
| 15 | - /cli/v10/cli-commands/find-dupes |
| 16 | - /cli/v10/cli-commands/npm-find-dupes |
| 17 | - /cli/v10/commands/find-dupes |
| 18 | - /cli/v10/find-dupes |
| 19 | - /cli/v10/npm-find-dupes |
| 20 | --- |
| 21 | |
| 22 | ### Synopsis |
| 23 | |
| 24 | ```bash |
| 25 | npm find-dupes |
| 26 | ``` |
| 27 | |
| 28 | ### Description |
| 29 | |
| 30 | Runs `npm dedupe` in `--dry-run` mode, making npm only output the duplications, without actually changing the package tree. |
| 31 | |
| 32 | ### Configuration |
| 33 | |
| 34 | #### `install-strategy` |
| 35 | |
| 36 | - Default: "hoisted" |
| 37 | - Type: "hoisted", "nested", "shallow", or "linked" |
| 38 | |
| 39 | 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. |
| 40 | |
| 41 | #### `legacy-bundling` |
| 42 | |
| 43 | - Default: false |
| 44 | - Type: Boolean |
| 45 | - DEPRECATED: This option has been deprecated in favor of `--install-strategy=nested` |
| 46 | |
| 47 | 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`. |
| 48 | |
| 49 | #### `global-style` |
| 50 | |
| 51 | - Default: false |
| 52 | - Type: Boolean |
| 53 | - DEPRECATED: This option has been deprecated in favor of `--install-strategy=shallow` |
| 54 | |
| 55 | Only install direct dependencies in the top level `node_modules`, but hoist on deeper dependencies. Sets `--install-strategy=shallow`. |
| 56 | |
| 57 | #### `strict-peer-deps` |
| 58 | |
| 59 | - Default: false |
| 60 | - Type: Boolean |
| 61 | |
| 62 | 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. |
| 63 | |
| 64 | 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. |
| 65 | |
| 66 | 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. |
| 67 | |
| 68 | #### `package-lock` |
| 69 | |
| 70 | - Default: true |
| 71 | - Type: Boolean |
| 72 | |
| 73 | If set to false, then ignore `package-lock.json` files when installing. This will also prevent _writing_ `package-lock.json` if `save` is true. |
| 74 | |
| 75 | #### `omit` |
| 76 | |
| 77 | - Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty. |
| 78 | - Type: "dev", "optional", or "peer" (can be set multiple times) |
| 79 | |
| 80 | Dependency types to omit from the installation tree on disk. |
| 81 | |
| 82 | 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. |
| 83 | |
| 84 | If a package type appears in both the `--include` and `--omit` lists, then it will be included. |
| 85 | |
| 86 | If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. |
| 87 | |
| 88 | #### `include` |
| 89 | |
| 90 | - Default: |
| 91 | - Type: "prod", "dev", "optional", or "peer" (can be set multiple times) |
| 92 | |
| 93 | Option that allows for defining which types of dependencies to install. |
| 94 | |
| 95 | This is the inverse of `--omit=<type>`. |
| 96 | |
| 97 | Dependency types specified in `--include` will not be omitted, regardless of the order in which omit/include are specified on the command-line. |
| 98 | |
| 99 | #### `ignore-scripts` |
| 100 | |
| 101 | - Default: false |
| 102 | - Type: Boolean |
| 103 | |
| 104 | If true, npm does not run scripts specified in package.json files. |
| 105 | |
| 106 | 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. |
| 107 | |
| 108 | #### `audit` |
| 109 | |
| 110 | - Default: true |
| 111 | - Type: Boolean |
| 112 | |
| 113 | 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 audit`](/cli/v10/commands/npm-audit) for details on what is submitted. |
| 114 | |
| 115 | #### `bin-links` |
| 116 | |
| 117 | - Default: true |
| 118 | - Type: Boolean |
| 119 | |
| 120 | Tells npm to create symlinks (or `.cmd` shims on Windows) for package executables. |
| 121 | |
| 122 | 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. |
| 123 | |
| 124 | #### `fund` |
| 125 | |
| 126 | - Default: true |
| 127 | - Type: Boolean |
| 128 | |
| 129 | When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/cli/v10/commands/npm-fund) for details. |
| 130 | |
| 131 | #### `workspace` |
| 132 | |
| 133 | - Default: |
| 134 | - Type: String (can be set multiple times) |
| 135 | |
| 136 | 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. |
| 137 | |
| 138 | Valid values for the `workspace` config are either: |
| 139 | |
| 140 | - Workspace names |
| 141 | - Path to a workspace directory |
| 142 | - Path to a parent workspace directory (will result in selecting all workspaces within that folder) |
| 143 | |
| 144 | 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. |
| 145 | |
| 146 | This value is not exported to the environment for child processes. |
| 147 | |
| 148 | #### `workspaces` |
| 149 | |
| 150 | - Default: null |
| 151 | - Type: null or Boolean |
| 152 | |
| 153 | Set to true to run the command in the context of **all** configured workspaces. |
| 154 | |
| 155 | Explicitly setting this to false will cause commands like `install` to ignore workspaces altogether. When not set explicitly: |
| 156 | |
| 157 | - 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. |
| 158 | |
| 159 | This value is not exported to the environment for child processes. |
| 160 | |
| 161 | #### `include-workspace-root` |
| 162 | |
| 163 | - Default: false |
| 164 | - Type: Boolean |
| 165 | |
| 166 | Include the workspace root when workspaces are enabled for a command. |
| 167 | |
| 168 | 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. |
| 169 | |
| 170 | This value is not exported to the environment for child processes. |
| 171 | |
| 172 | #### `install-links` |
| 173 | |
| 174 | - Default: false |
| 175 | - Type: Boolean |
| 176 | |
| 177 | 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. |
| 178 | |
| 179 | ### See Also |
| 180 | |
| 181 | - [npm dedupe](/cli/v10/commands/npm-dedupe) |
| 182 | - [npm ls](/cli/v10/commands/npm-ls) |
| 183 | - [npm update](/cli/v10/commands/npm-update) |
| 184 | - [npm install](/cli/v10/commands/npm-install) |