It's unnecessary noise and somewhat confusing. Only real change here is a minor version bump for grunt-contrib-jshint. Which was noticed by the @sindresorhus and now he did not get credit for it. I'm sure @sindresorhus is cool with it, but if it was someone else, he could get upset. So i would suggest to not mix up this kind of changes whenever they are in same plane or not.
@markelog Ok, I get the noise argument. As for giving credit... Come on, if anyone gets upset because of not being credited for a minor version bump, I'd say they have a problem with themselves.
OTH, sth like #1405 or #1407 definitely deserves credit.
@FagnerMartinsBrack I've already replied to @markelog that that's true. ;) grunt-contrib-jshint had to be updated as the minor version, not the patch version changed.
@markelog I've just checked and packages specified with ~ don't auto-update themselves. What is done is if you're missing a package it will install the latest matching one but if you already have one, npm install won't update it. IMO it means that updating dependencies manually makes sense as new patch versions usually fix bugs.
@scottgonzalez +1. I'm willing to update dependencies manually from time to time myself.
On the other hand, providing specific version numbers is not a universal remedy. Those packages have their own dependencies and they are often provided in a non-strict way so we'll still be left with non-consistent package versions and there's no way around that. If node_modules was a small directory we could as well commit it to the repo but it's not, it's huge so it won't happen.
Unfortunately, npm doesn't have an analogue of gem's Gemfile.lock that provides the whole tree of mappings package -> version number. I consider it one of npm's major faults.
@mzgol npm does have shrinkwrap, but I agree with @dmethvin that it's overkill for our needs.
While Grunt 0.3 -> 0.4 is a good example of the code breaking on us, we wouldn't have that specific problem with the ranges currently listed, since ~0.3.0 wouldn't match an 0.4 release.
But we've been bitten by bugs introduced in patch versions of our dependencies. We all know software isn't perfect, and bugs introduced through version ranges are often tricky to track down.
IMO it means that updating dependencies manually makes sense as new patch versions usually fix bugs.
No, it does not. If you already has installed npm packages and you want to update them, you should use npm update not npm install. Hence the name.
I'm willing to update dependencies manually from time to time myself.
Then what's the point of tilde removal? If you just gonna do it manually? I say let's remove tilde and use specific versions, update patch version of the package if we noticed some bugs with it, but only if update would help, or if it has new minor or major versions, we could even automate it through build task and irc bot.
I don't mind doing these kind of dependency updates manually when they're needed, to fix bugs that affect us. Doing it automatically just leads back to the same headaches we are trying to avoid by using imprecise dependency specs like ~ or >=.
@mzgol Why did you update these dependencies? They have
~so we would not do so