1NPM-FIND-DUPES(1) NPM-FIND-DUPES(1)
2
6 npm-find-dupes - Find duplication in the package tree
7 Synopsis
9 npm find-dupes
10 Description
12 Runs npm dedupe in --dry-run mode, making npm only output the duplica‐
13 tions, without actually changing the package tree.
14 Configuration
16 <!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> <!-- automatically
17 generated, do not edit manually --> <!-- see lib/utils/config/defini‐
18 tions.js -->
19 global-style
21 • Default: false
22 • Type: Boolean
24 Causes npm to install the package into your local node_modules folder
27 with the same layout it uses with the global node_modules folder. Only
28 your direct dependencies will show in node_modules and everything they
29 depend on will be flattened in their node_modules folders. This obvi‐
30 ously will eliminate some deduping. If used with legacy-bundling,
31 legacy-bundling will be preferred. <!-- automatically generated, do
32 not edit manually --> <!-- see lib/utils/config/definitions.js -->
33 legacy-bundling
36 • Default: false
37 • Type: Boolean
39 Causes npm to install the package such that versions of npm prior to
42 1.4, such as the one included with node 0.8, can install the package.
43 This eliminates all automatic deduping. If used with global-style this
44 option will be preferred. <!-- automatically generated, do not edit
45 manually --> <!-- see lib/utils/config/definitions.js -->
46 strict-peer-deps
49 • Default: false
50 • Type: Boolean
52 If set to true, and --legacy-peer-deps is not set, then any conflicting
55 peerDependencies will be treated as an install failure, even if npm
56 could reasonably guess the appropriate resolution based on non-peer de‐
57 pendency relationships.
58 By default, conflicting peerDependencies deep in the dependency graph
60 will be resolved using the nearest non-peer dependency specification,
61 even if doing so will result in some packages receiving a peer depen‐
62 dency outside the range set in their package's peerDependencies object.
63 When such and override is performed, a warning is printed, explaining
65 the conflict and the packages involved. If --strict-peer-deps is set,
66 then this warning is treated as a failure. <!-- automatically gener‐
67 ated, do not edit manually --> <!-- see lib/utils/config/definitions.js
68 -->
69 package-lock
72 • Default: true
73 • Type: Boolean
75 If set to false, then ignore package-lock.json files when installing.
78 This will also prevent writing package-lock.json if save is true.
79 When package package-locks are disabled, automatic pruning of extrane‐
81 ous modules will also be disabled. To remove extraneous modules with
82 package-locks disabled use npm prune. <!-- automatically generated, do
83 not edit manually --> <!-- see lib/utils/config/definitions.js -->
84 omit
87 • Default: 'dev' if the NODE_ENV environment variable is set to 'pro‐
88 duction', otherwise empty.
89 • Type: "dev", "optional", or "peer" (can be set multiple times)
91 Dependency types to omit from the installation tree on disk.
94 Note that these dependencies are still resolved and added to the pack‐
96 age-lock.json or npm-shrinkwrap.json file. They are just not physically
97 installed on disk.
98 If a package type appears in both the --include and --omit lists, then
100 it will be included.
101 If the resulting omit list includes 'dev', then the NODE_ENV environ‐
103 ment variable will be set to 'production' for all lifecycle scripts.
104 <!-- automatically generated, do not edit manually --> <!-- see
105 lib/utils/config/definitions.js -->
106 ignore-scripts
109 • Default: false
110 • Type: Boolean
112 If true, npm does not run scripts specified in package.json files.
115 Note that commands explicitly intended to run a particular script, such
117 as npm start, npm stop, npm restart, npm test, and npm run-script will
118 still run their intended script if ignore-scripts is set, but they will
119 not run any pre- or post-scripts. <!-- automatically generated, do not
120 edit manually --> <!-- see lib/utils/config/definitions.js -->
121 audit
124 • Default: true
125 • Type: Boolean
127 When "true" submit audit reports alongside the current npm command to
130 the default registry and all registries configured for scopes. See the
131 documentation for npm help audit for details on what is submitted.
132 <!-- automatically generated, do not edit manually --> <!-- see
133 lib/utils/config/definitions.js -->
134 bin-links
137 • Default: true
138 • Type: Boolean
140 Tells npm to create symlinks (or .cmd shims on Windows) for package ex‐
143 ecutables.
144 Set to false to have it not do this. This can be used to work around
146 the fact that some file systems don't support symlinks, even on osten‐
147 sibly Unix systems. <!-- automatically generated, do not edit manually
148 --> <!-- see lib/utils/config/definitions.js -->
149 fund
152 • Default: true
153 • Type: Boolean
155 When "true" displays the message at the end of each npm install ac‐
158 knowledging the number of dependencies looking for funding. See npm
159 help npm fund for details. <!-- automatically generated, do not edit
160 manually --> <!-- see lib/utils/config/definitions.js -->
161 workspace
164 • Default:
165 • Type: String (can be set multiple times)
167 Enable running a command in the context of the configured workspaces of
170 the current project while filtering by running only the workspaces de‐
171 fined by this configuration option.
172 Valid values for the workspace config are either:
174 • Workspace names
176 • Path to a workspace directory
178 • Path to a parent workspace directory (will result in selecting all
180 workspaces within that folder)
181 When set for the npm init command, this may be set to the folder of a
184 workspace which does not yet exist, to create the folder and set it up
185 as a brand new workspace within the project.
186 This value is not exported to the environment for child processes.
188 <!-- automatically generated, do not edit manually --> <!-- see
189 lib/utils/config/definitions.js -->
190 workspaces
193 • Default: null
194 • Type: null or Boolean
196 Set to true to run the command in the context of all configured
199 workspaces.
200 Explicitly setting this to false will cause commands like install to
202 ignore workspaces altogether. When not set explicitly:
203 • Commands that operate on the node_modules tree (install, update,
205 etc.) will link workspaces into the node_modules folder. - Commands
206 that do other things (test, exec, publish, etc.) will operate on the
207 root project, unless one or more workspaces are specified in the
208 workspace config.
209 This value is not exported to the environment for child processes.
212 <!-- automatically generated, do not edit manually --> <!-- see
213 lib/utils/config/definitions.js -->
214 include-workspace-root
217 • Default: false
218 • Type: Boolean
220 Include the workspace root when workspaces are enabled for a command.
223 When false, specifying individual workspaces via the workspace config,
225 or all workspaces via the workspaces flag, will cause npm to operate
226 only on the specified workspaces, and not on the root project. <!--
227 automatically generated, do not edit manually --> <!-- see
228 lib/utils/config/definitions.js -->
229 <!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
231 See Also
234 • npm help dedupe
235 • npm help ls
237 • npm help update
239 • npm help install
241 January 2022 NPM-FIND-DUPES(1)