Re:Fix the versioning
by tedunangst on Friday August 29, 2014 @06:25PM
(#8244785)
Yes. Not that I had any plans to write node modules, but I sure as fuck don't want to now, lest somebody discover my work and start using it and then telling me how I need to do things.
[ Parent
| on HN ]
https://www.npmjs.org/browse/depended
_ is the most depended on node.js module. Maintainer, Ashkenas, introduced breaking changes. By default npm will pull down these changes without prompting because it was designed to follow semver. Maybe npm is at fault. Maybe it's Ashkenas.
However, Ashkenas knows his change is going to break people and just doesn't care.
Re:Fix the versioning
by tedunangst on Friday August 29, 2014 @06:55PM
(#8244890)
Did the same thing not happen with 1.6? And 1.5? Who thought 1.7 would be different?
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.
I suppose I shouldn't start new projects, either?
How does that follow?
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.