Searches the local package tree and attempts to simplify the overall
structure by moving dependencies further up the tree, where they can
be more effectively shared by multiple dependent packages.
For example, consider this dependency graph:
+-- b <-- depends on email@example.com
| -- firstname.lastname@example.org
-- d <-- depends on c@~1.0.9
In this case, npm help npm-dedupe will transform the tree to:
Because of the hierarchical nature of nodes module lookup, b and d
will both get their dependency met by the single c package at the root
level of the tree.
If a suitable version exists at the target location in the tree
already, then it will be left untouched, but the other duplicates will
If no suitable version can be found, then a warning is printed, and
nothing is done.
If any arguments are supplied, then they are filters, and only the
named packages will be touched.
Note that this operation transforms the dependency tree, and may
result in packages getting updated versions, perhaps from the npm
This feature is experimental, and may change in future versions.
The --tag argument will apply to all of the affected dependencies. If a
tag with the given name exists, the tagged version is preferred over newer