News for hackers. Stuff that matters.
Re:Flat Tree Dependency Resolution in Npm v3 by tlrobinson on Thursday December 31, 2015 @03:35PM (#10819545)
"dependency resolution depends on install order"

Does this sound insane to anyone else?

EDIT: I understand not wanting to modify node's `require` semantics, but this is an unacceptable sacrifice of consistency for efficiency. Surely it would have been possible for an `npm install --save x` to put the `node_modules` directory in a state identical to `npm install --save x && rm -rf node_modules && npm install`. It might take a little longer to shuffle some directories around, but certainly not longer than a full `npm install`.

Re:Flat Tree Dependency Resolution in Npm v3 by frank-weindel on Friday January 01, 2016 @01:46AM (#10821281)
What's more is that standard `npm install` install order is ALWAYS alphabetic. Which causes some packages, purely arbitrarily, to influence directory structure.
Re:Flat Tree Dependency Resolution in Npm v3 by paulddraper on Thursday December 31, 2015 @05:53PM (#10820171)
Surely they will have to change that. Right? It can't last long.
Re:Flat Tree Dependency Resolution in Npm v3 by hakcermani on Thursday December 31, 2015 @04:42PM (#10819848)
Totally. That was the first thing that stuck out to me.