> Err... isn't the whole point of a big number release to introduce big, breaking changes?
Certainly not. Breaking changes should still be avoided as much as possible.
Certainly not. Breaking changes should still be avoided as much as possible.
Not saying every project can do it, but some of these ESLint changes seem rather unnecessary.
React always adds warnings in 1 major release and then removes in the following major release, meaning if you have no warnings you can just upgrade without fear, which is quite a nice way of doing it.
I agree that the way React does things is preferable.