News for hackers. Stuff that matters.
Re:Yarn – A new package manager for JavaScript by ksherlock on Tuesday October 11, 2016 @02:44PM (#12687351)
nesting can't be prevented in that case (at least with the current node require() design). It gets really bad if you have 10 packages that depend on [email protected] and 10 packages that depend on [email protected] -- one of them will install in the root directory and the other 10 will be duplicated. ied stores a single copy of each package@version and uses symlinks which is an improvement. Apparently yarn tried something similar but it breaks some packages (that check where they're located for example).

https://github.com/alexanderGugel/ied

Re:Yarn – A new package manager for JavaScript by Osiris on Tuesday October 11, 2016 @04:25PM (#12688218)
I could be prevented. Another project does this by using a hash of the project to all all dependencies at one level then symlinks the dependencies from hash to name so it references the correct version.