4 ms·
You are correct, this was voluntary. It was the difficulty level of the upgrade that was frustrating. We also love the NPM known vulnerability scanner, and we
by sammorrowdrums 8y ago
You are correct, this was voluntary. It was the difficulty level of the upgrade that was frustrating.
We also love the NPM known vulnerability scanner, and we managed to get down to zero known vulns in our deps, we like the direction of React, and Bootstrap and some other things. We want to be a good citizen and use recent versions of software, partly to play our part and decrease the maintenance burden for old versions of things, but also when we feel that holding back the tide will not help us.
Webpack has also got a lot nicer, the defaults are getting better. Its opinionated starting point philosophy is good, and did let us simplify a lot of config, and speed up builds etc.
I'm willing to accept that I'm grumbling, and perhaps the trade-off of better software but more serious breaking changes is worthwhile, but I think it could have been avoided if there was more of a focus on trying to bridge versions of React. It would be nice to be able to upgrade React and focus primarily on how that might affect my own code, than having to chase down all the deps that don't straddle versions.