News for hackers. Stuff that matters.
Re:Fix the versioning by __david__ on Friday August 29, 2014 @09:54PM (#8245314)
Or perhaps the fault lies with the people who update their dependencies blindly and then don't run tests. Not locking your dependencies down is a recipe for breakage.
Re:Fix the versioning by iends on Saturday August 30, 2014 @08:30AM (#8246267)
I suppose I shouldn't start new projects, either?
Re:Fix the versioning by __david__ on Monday September 08, 2014 @04:07PM (#8286925)
How does that follow?
Re:Fix the versioning by iends on Monday September 08, 2014 @04:24PM (#8287006)
When you started a new project and pulled down new packages, all the packages that depended on underscore functionality that changed were broken because of this change. That's because NPM makes assumptions about major/minor versions and those packages pulled down the incompatible version.

You can suggested that every package on npm vender their own dependencies, but in practice nobody does this because npm is known to make these assumptions.