No offense! I'm not complaining about the package being changed; especially since i don't use it.
I just found the way a bit strange. but that's not really the issue for me either.
The volatility of npm and how many people are using it worries me more.
It is a strange response, but I feel more grated by the attitudes of so many devs who obviously are upset when their slave labor doesn't comply with their every whim.
NPM is unreasonably volatile. Whoever is just updating blind (esp. with packages whose maker explicitly stated to fork or pay up with a years warning) are skipping through a minefield, I struggle to feel sorry for them when things blow up in their face.
No offense! I'm not complaining about the package being changed; especially since i don't use it.
I just found the way a bit strange. but that's not really the issue for me either.
The volatility of npm and how many people are using it worries me more.
Thanks for enduring my snark; sorry about that!
It is a strange response, but I feel more grated by the attitudes of so many devs who obviously are upset when their slave labor doesn't comply with their every whim.
NPM is unreasonably volatile. Whoever is just updating blind (esp. with packages whose maker explicitly stated to fork or pay up with a years warning) are skipping through a minefield, I struggle to feel sorry for them when things blow up in their face.
I agree with you. The expectations of free software are sometimes unbearable.