The next release of React, version 16, will include a complete rewrite of React's internals along with other improvements to its usefulness. The rewrite has resulted in the need for the changes in React 15.5.
The first major change comes in the form of deprecation warnings when you use eact.PropTypes or React.createClass. The warnings are raised because the developers have extracted both React.PropTypes and React.createClass into their own packages. Both are still accessible via the main React object, but using either will log a one-time deprecation warning to the console when in development mode. This will enable future code size optimizations.
Writing about the new version, Andrew Clark, part of the Reactjs core team at Facebook, says:
"Adding new warnings is not something we do lightly. Warnings in React are not mere suggestions — they are integral to our strategy of keeping as many people as possible on the latest version of React. We never add warnings without providing an incremental path forward.
So while the warnings may cause frustration in the short-term, we believe prodding developers to migrate their codebases now prevents greater frustration in the future."
The idea is that you should fix code that causes warnings in this version, and if your app produces no warnings in 15.5, it should continue to work in 16 without any changes.
The developers have provided a codemod to automatically change your code for each of the new deprecations.
Another change announced with React 15.5 is the cessation of active maintenance of React Addons packages. The developers say that in point of fact, most of the packages haven't been actively maintained in a long time, and they should continue to work indefinitely, but the developers recommend migrating away as soon as you can to prevent future breakages.
The results of the 2017 Stack Overflow survey are available. They cover many different aspects of the developer landscape and one that is of immediate interest is what we can expect to be paid and whe [ ... ]