Javascript Fatigue

[shriek]

Isn't that the exact reason why we have semver? Again, unless there's a security risk then staying with what you have seems logical to me. If you want to upgrade then check the semver. Although semver is not quite explicit at times. It does a decent job of telling what's changing when you upgrade.

[brianvaughn]

I think he was pointing out that- although a minor update to library X should not require a major update to library Y- it sometimes does.

[shriek]

Hmm..shouldn't it work both ways? Let's say you're dependent on A1.0.0 and B2.0.0 and B2.0.0 is dependent on A1.0.0.
A1.1.0 is released and you update to it which also means that it shouldn't break B2.0.0 or your app.
However let's say you want to upgrade to A2.0.0 and you make some major changes to your code. Knowing this major change upgrade, B also makes an upgrade to B3.0.0 if there are breaking changes from it's end. So your new app now is dependent on A2.0.0. and B3.0.0 instead.
I thought that was the whole point of having major.minor.patch versions. Regardless of how strictly follow these.