@cryptotaxi247 / documentation-1
Code Commits Issues Pulls Sessions CI/CD
deprecate-totp-2fa
@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 166 lines 6.5 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/v8
7 github_path: docs/lib/content/commands/npm-find-dupes.md
8 redirect_from:
9 - /cli-documentation/v8/cli-commands/find-dupes
10 - /cli-documentation/v8/cli-commands/npm-find-dupes
11 - /cli-documentation/v8/commands/find-dupes
12 - /cli-documentation/v8/commands/npm-find-dupes
13 - /cli-documentation/v8/find-dupes
14 - /cli-documentation/v8/npm-find-dupes
15 - /cli/v8/cli-commands/find-dupes
16 - /cli/v8/cli-commands/npm-find-dupes
17 - /cli/v8/commands/find-dupes
18 - /cli/v8/find-dupes
19 - /cli/v8/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 #### `global-style`
35
36 - Default: false
37 - Type: Boolean
38
39 Causes npm to install the package into your local `node_modules` folder with the same layout it uses with the global `node_modules` folder. Only your direct dependencies will show in `node_modules` and everything they depend on will be flattened in their `node_modules` folders. This obviously will eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be preferred.
40
41 #### `legacy-bundling`
42
43 - Default: false
44 - Type: Boolean
45
46 Causes npm to install the package such that versions of npm prior to 1.4, such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with `global-style` this option will be preferred.
47
48 #### `strict-peer-deps`
49
50 - Default: false
51 - Type: Boolean
52
53 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.
54
55 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.
56
57 When such and 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.
58
59 #### `package-lock`
60
61 - Default: true
62 - Type: Boolean
63
64 If set to false, then ignore `package-lock.json` files when installing. This will also prevent _writing_ `package-lock.json` if `save` is true.
65
66 This configuration does not affect `npm ci`.
67
68 #### `omit`
69
70 - Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.
71 - Type: "dev", "optional", or "peer" (can be set multiple times)
72
73 Dependency types to omit from the installation tree on disk.
74
75 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.
76
77 If a package type appears in both the `--include` and `--omit` lists, then it will be included.
78
79 If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts.
80
81 #### `ignore-scripts`
82
83 - Default: false
84 - Type: Boolean
85
86 If true, npm does not run scripts specified in package.json files.
87
88 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.
89
90 #### `audit`
91
92 - Default: true
93 - Type: Boolean
94
95 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/v8/commands/npm-audit) for details on what is submitted.
96
97 #### `bin-links`
98
99 - Default: true
100 - Type: Boolean
101
102 Tells npm to create symlinks (or `.cmd` shims on Windows) for package executables.
103
104 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.
105
106 #### `fund`
107
108 - Default: true
109 - Type: Boolean
110
111 When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/cli/v8/commands/npm-fund) for details.
112
113 #### `workspace`
114
115 - Default:
116 - Type: String (can be set multiple times)
117
118 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.
119
120 Valid values for the `workspace` config are either:
121
122 - Workspace names
123 - Path to a workspace directory
124 - Path to a parent workspace directory (will result in selecting all workspaces within that folder)
125
126 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.
127
128 This value is not exported to the environment for child processes.
129
130 #### `workspaces`
131
132 - Default: null
133 - Type: null or Boolean
134
135 Set to true to run the command in the context of **all** configured workspaces.
136
137 Explicitly setting this to false will cause commands like `install` to ignore workspaces altogether. When not set explicitly:
138
139 - 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.
140
141 This value is not exported to the environment for child processes.
142
143 #### `include-workspace-root`
144
145 - Default: false
146 - Type: Boolean
147
148 Include the workspace root when workspaces are enabled for a command.
149
150 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.
151
152 This value is not exported to the environment for child processes.
153
154 #### `install-links`
155
156 - Default: false
157 - Type: Boolean
158
159 When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.
160
161 ### See Also
162
163 - [npm dedupe](/cli/v8/commands/npm-dedupe)
164 - [npm ls](/cli/v8/commands/npm-ls)
165 - [npm update](/cli/v8/commands/npm-update)
166 - [npm install](/cli/v8/commands/npm-install)