Seriously, what in the 7 hells am I doing wrong here? Because the error messages of npm are really NOT helpful.
Here’s where npm has bit me in the past:
a) Updating packages to a new version where other packages explicitly stated that they still depend on the older version. This leads to fun times (i.e. everything not working).
b) Not updating packages at all. This lead me to create a bug report with the author’s answer: “That’s been fixed 10 releases ago. What version are you running?” and me realizing that just because I ran
npm update 5 minutes ago, this obviously doesn’t mean that it really updated anything. And, no, it doesn’t tell you that there are new versions available. Had to fix this by editing package.json by hand.
c) Or the part where it does update some packages but not all of the packages. Again, broken site.
d) Or the part where it updates packages but does not pull in new dependencies. Because raisins. Can you say: broken site?
Seriously, is it so hard to NOT update packages when you find out about dependency issues? You could simply tell the users, in PLAIN, easy to understand sentences:
New version for ABC is available, the dependencies MNO and XYZ do not have updated versions available yet.
Also, package DCE depends on version x.y.z of ABC
If you want to update anyway, please add the parameter --force
And not this console.log diarrhea where you need some kind of CompSci degree to make sense of what depends on whom.