3 ms·
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 bre
by __david__ 12y ago
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.
- iends 12y agoI suppose I shouldn't start new projects, either?
- __david__ 12y agoHow does that follow?
- iends 12y agoWhen 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.