@cryptotaxi247 / documentation-1
Code Commits Issues Pulls Sessions CI/CD
maitxn/version-bump-tar
@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
mdx 173 lines 6.84 KB
Raw
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/v9
7 github_path: docs/lib/content/commands/npm-find-dupes.md
8 redirect_from:
9 - /cli-documentation/v9/cli-commands/find-dupes
10 - /cli-documentation/v9/cli-commands/npm-find-dupes
11 - /cli-documentation/v9/commands/find-dupes
12 - /cli-documentation/v9/commands/npm-find-dupes
13 - /cli-documentation/v9/find-dupes
14 - /cli-documentation/v9/npm-find-dupes
15 - /cli/v9/cli-commands/find-dupes
16 - /cli/v9/cli-commands/npm-find-dupes
17 - /cli/v9/commands/find-dupes
18 - /cli/v9/find-dupes
19 - /cli/v9/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 #### `ignore-scripts`
89
90 - Default: false
91 - Type: Boolean
92
93 If true, npm does not run scripts specified in package.json files.
94
95 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.
96
97 #### `audit`
98
99 - Default: true
100 - Type: Boolean
101
102 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/v9/commands/npm-audit) for details on what is submitted.
103
104 #### `bin-links`
105
106 - Default: true
107 - Type: Boolean
108
109 Tells npm to create symlinks (or `.cmd` shims on Windows) for package executables.
110
111 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.
112
113 #### `fund`
114
115 - Default: true
116 - Type: Boolean
117
118 When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/cli/v9/commands/npm-fund) for details.
119
120 #### `workspace`
121
122 - Default:
123 - Type: String (can be set multiple times)
124
125 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.
126
127 Valid values for the `workspace` config are either:
128
129 - Workspace names
130 - Path to a workspace directory
131 - Path to a parent workspace directory (will result in selecting all workspaces within that folder)
132
133 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.
134
135 This value is not exported to the environment for child processes.
136
137 #### `workspaces`
138
139 - Default: null
140 - Type: null or Boolean
141
142 Set to true to run the command in the context of **all** configured workspaces.
143
144 Explicitly setting this to false will cause commands like `install` to ignore workspaces altogether. When not set explicitly:
145
146 - 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.
147
148 This value is not exported to the environment for child processes.
149
150 #### `include-workspace-root`
151
152 - Default: false
153 - Type: Boolean
154
155 Include the workspace root when workspaces are enabled for a command.
156
157 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.
158
159 This value is not exported to the environment for child processes.
160
161 #### `install-links`
162
163 - Default: false
164 - Type: Boolean
165
166 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.
167
168 ### See Also
169
170 - [npm dedupe](/cli/v9/commands/npm-dedupe)
171 - [npm ls](/cli/v9/commands/npm-ls)
172 - [npm update](/cli/v9/commands/npm-update)
173 - [npm install](/cli/v9/commands/npm-install)