News for hackers. Stuff that matters.
[deleted]
Re:Flat Tree Dependency Resolution in Npm v3 by tedmiston on Thursday December 31, 2015 @12:50PM (#10818687)
Not really -- unless you want to fork each top-level dependency and update the common dependencies to the latest common subversion in package.json (and maintain that). Far from ideal IMO.
Re:Flat Tree Dependency Resolution in Npm v3 by Killswitch on Thursday December 31, 2015 @12:21PM (#10818525)
While I can understand the want for that, there's too much issues. The only reason npm does it this way is because the module that depends on B v1.3 and a module that depends on B v2.1 could be introducing some really bad bugs or breakage if you force all modules to use B v2.1.

That's one of the reason bower is losing out.

Re:Flat Tree Dependency Resolution in Npm v3 by ag_dubs on Thursday December 31, 2015 @12:56PM (#10818718)
forcing a single copy of a dep is exactly the opposite of the dependency strategy both the node module loader and npm take. the fact that the node module loader can load more than one version of a module into memory is its strength and npm plays to this, and in doing so avoids "dependency hell". you might checkout this page in the docs that talks more about this: https://docs.npmjs.com/how-npm-works/npm2