3 ms·
> Minor revision releases will include deprecation warnings and tips for how to upgrade an API or pattern that will be removed or changed in the future. 16.3 i
by audiolion 9y ago
> Minor revision releases will include deprecation warnings and tips for how to upgrade an API or pattern that will be removed or changed in the future.
16.3 is including dep warnings and tips to upgrade, check.
> We will continue to release codemods for common patterns to make automatic upgrades of your codebase easier.
Probably will be there closer to 17 release.
> Once we’ve reached the end of life for a particular major version, we’ll release a new major version where all deprecated APIs have been remove
Once 16.x end of life is reached, the next major version, 17, will remove the deprecated APIs, check.
They are literally following exactly what they said.
- danabramov 9y agoNote 16.3 doesn’t even include warnings. We are only adding support for the new aliases at this point, but won't fire warnings until the biggest ecosystem libraries have updated with recommendations in the blog post. Yes, there will also be a codemod for the "UNSAFE_" rename.
- brianvaughn 9y agoOne of the main focuses of 16.3 is to enable open source libraries to update their code in advance of deprecation warnings. (We're trying to go one step beyond SEMVER- so that application developers don't have to be bothered by warnings in third party code that they can't change.) And the codemod has already been released: https://github.com/reactjs/react-codemod#rename-unsafe-lifecycles https://github.com/reactjs/react-codemod#rename-unsafe-lifec... We've used it internally (at Facebook) to update ~14,000 components already, so it's well tested.
- deleted 9y ago[deleted]