3 ms·
It's actually not. There are some lifecycle changes, potential modifications to setState (async only), etc. That's why it's being released as a new major versio
by b34r 10y ago
It's actually not. There are some lifecycle changes, potential modifications to setState (async only), etc. That's why it's being released as a new major version.
- cheapsteak 10y agoI think we may be splitting hairs over the definition of API compatibility
- antjanus 9y agoit's one of those 99% compatible except for a few small quirks that only developers using it on large applications will notice. The React devs have also been great with releasing codemods for breaking APIs.
- danabramov 9y agosetState is not async-only in React 16. We keep the old behavior and just change the engine now. Later we will look into enabling new behavior.