npm/npm — pull request #6954 by ide (2014-12-17 00:21:39+00:00)
Title: Don't warn about identical duplicates between dependencies and devDependencies

Sometimes the same package will be listed as both a dependency and a
devDependency. Currently `npm install` prints a warning about this and says it
will use the version listed under `dependencies`. This diff removes that warning
when the versions are the exact same so there's no chance of conflict.

The reason for suppressing the warning is that I think it is legit to have the
same package as a dependency and a devDependency so you can be explicit about
what uses the package. That way if you stop using the package in your published
code but still use it from your build code, you can just remove the entry from
`dependencies` and leave it in `devDependencies`.

Tested by running `node cli.js install` on a package.json file with the same
dependency (exact same version) under `dependencies` and `devDependencies`.