npm-find-dupes(1)

1NPM-FIND-DUPES(1)                                            NPM-FIND-DUPES(1)
2
3
4

NAME

6       npm-find-dupes - Find duplication in the package tree
7
8   Synopsis
9         npm find-dupes
10
11   Description
12       Runs  npm dedupe in --dry-run mode, making npm only output the duplica‐
13       tions, without actually changing the package tree.
14
15   Configuration
16   global-style
17       • Default: false
18
19       • Type: Boolean
20
21
22       Causes npm to install the package into your local  node_modules  folder
23       with  the same layout it uses with the global node_modules folder. Only
24       your direct dependencies will show in node_modules and everything  they
25       depend  on  will be flattened in their node_modules folders. This obvi‐
26       ously will eliminate  some  deduping.  If  used  with  legacy-bundling,
27       legacy-bundling will be preferred.
28
29   legacy-bundling
30       • Default: false
31
32       • Type: Boolean
33
34
35       Causes  npm  to  install the package such that versions of npm prior to
36       1.4, such as the one included with node 0.8, can install  the  package.
37       This  eliminates all automatic deduping. If used with global-style this
38       option will be preferred.
39
40   strict-peer-deps
41       • Default: false
42
43       • Type: Boolean
44
45
46       If set to true, and --legacy-peer-deps is not set, then any conflicting
47       peerDependencies  will  be  treated  as an install failure, even if npm
48       could reasonably guess the appropriate resolution based on non-peer de‐
49       pendency relationships.
50
51       By  default,  conflicting peerDependencies deep in the dependency graph
52       will be resolved using the nearest non-peer  dependency  specification,
53       even  if  doing so will result in some packages receiving a peer depen‐
54       dency outside the range set in their package's peerDependencies object.
55
56       When such and override is performed, a warning is  printed,  explaining
57       the  conflict  and the packages involved. If --strict-peer-deps is set,
58       then this warning is treated as a failure.
59
60   package-lock
61       • Default: true
62
63       • Type: Boolean
64
65
66       If set to false, then ignore package-lock.json files  when  installing.
67       This will also prevent writing package-lock.json if save is true.
68
69       This configuration does not affect npm ci.
70
71   omit
72       • Default:  'dev'  if the NODE_ENV environment variable is set to 'pro‐
73         duction', otherwise empty.
74
75       • Type: "dev", "optional", or "peer" (can be set multiple times)
76
77
78       Dependency types to omit from the installation tree on disk.
79
80       Note that these dependencies are still resolved and added to the  pack‐
81       age-lock.json or npm-shrinkwrap.json file. They are just not physically
82       installed on disk.
83
84       If a package type appears in both the --include and --omit lists,  then
85       it will be included.
86
87       If  the  resulting omit list includes 'dev', then the NODE_ENV environ‐
88       ment variable will be set to 'production' for all lifecycle scripts.
89
90   ignore-scripts
91       • Default: false
92
93       • Type: Boolean
94
95
96       If true, npm does not run scripts specified in package.json files.
97
98       Note that commands explicitly intended to run a particular script, such
99       as  npm start, npm stop, npm restart, npm test, and npm run-script will
100       still run their intended script if ignore-scripts is set, but they will
101       not run any pre- or post-scripts.
102
103   audit
104       • Default: true
105
106       • Type: Boolean
107
108
109       When  "true"  submit audit reports alongside the current npm command to
110       the default registry and all registries configured for scopes. See  the
111       documentation for npm help audit for details on what is submitted.
112
113   bin-links
114       • Default: true
115
116       • Type: Boolean
117
118
119       Tells npm to create symlinks (or .cmd shims on Windows) for package ex‐
120       ecutables.
121
122       Set to false to have it not do this. This can be used  to  work  around
123       the  fact that some file systems don't support symlinks, even on osten‐
124       sibly Unix systems.
125
126   fund
127       • Default: true
128
129       • Type: Boolean
130
131
132       When "true" displays the message at the end of  each  npm  install  ac‐
133       knowledging  the  number  of  dependencies looking for funding. See npm
134       help npm fund for details.
135
136   workspace
137       • Default:
138
139       • Type: String (can be set multiple times)
140
141
142       Enable running a command in the context of the configured workspaces of
143       the  current project while filtering by running only the workspaces de‐
144       fined by this configuration option.
145
146       Valid values for the workspace config are either:
147
148       • Workspace names
149
150       • Path to a workspace directory
151
152       • Path to a parent workspace directory (will result  in  selecting  all
153         workspaces within that folder)
154
155
156       When  set  for the npm init command, this may be set to the folder of a
157       workspace which does not yet exist, to create the folder and set it  up
158       as a brand new workspace within the project.
159
160       This value is not exported to the environment for child processes.
161
162   workspaces
163       • Default: null
164
165       • Type: null or Boolean
166
167
168       Set  to  true  to  run  the  command  in  the context of all configured
169       workspaces.
170
171       Explicitly setting this to false will cause commands  like  install  to
172       ignore workspaces altogether. When not set explicitly:
173
174       • Commands  that  operate  on  the  node_modules tree (install, update,
175         etc.)  will link workspaces into the node_modules folder. -  Commands
176         that  do other things (test, exec, publish, etc.) will operate on the
177         root project, unless one or more  workspaces  are  specified  in  the
178         workspace config.
179
180
181       This value is not exported to the environment for child processes.
182
183   include-workspace-root
184       • Default: false
185
186       • Type: Boolean
187
188
189       Include the workspace root when workspaces are enabled for a command.
190
191       When  false, specifying individual workspaces via the workspace config,
192       or all workspaces via the workspaces flag, will cause  npm  to  operate
193       only on the specified workspaces, and not on the root project.
194
195       This value is not exported to the environment for child processes.
196
197   install-links
198       • Default: false
199
200       • Type: Boolean
201
202
203       When  set file: protocol dependencies that exist outside of the project
204       root will be packed and installed as regular  dependencies  instead  of
205       creating a symlink. This option has no effect on workspaces.
206
207   See Also
208       • npm help dedupe
209
210       • npm help ls
211
212       • npm help update
213
214       • npm help install
215
216
217
218
219                                September 2022               NPM-FIND-DUPES(1)