react-dom 16.0.0 release notes

semverse.

react-dom 16.0.0 release notes · Semverse

ReactDOM.createPortal()

Breaking Changes

There are several changes to the behavior of scheduling and lifecycle methods:
- ReactDOM.render() and ReactDOM.unstable_renderIntoContainer() now return null if called from inside a lifecycle method.
  - To work around this, you can either use the new portal API or refs.
- Minor changes to setState behavior:
  - Calling setState with null no longer triggers an update. This allows you to decide in an updater function if you want to re-render.
  - Calling setState directly in render always causes an update. This was not previously the case. Regardless, you should not be calling setState from render.
  - setState callback (second argument) now fires immediately after componentDidMount / componentDidUpdate instead of after all components have rendered.
- When replacing <A /> with <B />, B.componentWillMount now always happens before A.componentWillUnmount. Previously, A.componentWillUnmount could fire first in some cases.
- Previously, changing the ref to a component would always detach the ref before that component's render is called. Now, we change the ref later, when applying the changes to the DOM.
- It is not safe to re-render into a container that was modified by something other than React. This worked previously in some cases but was never supported. We now emit a warning in this case. Instead you should clean up your component trees using ReactDOM.unmountComponentAtNode. See this example.
- componentDidUpdate lifecycle no longer receives prevContext param. (@bvaughn in #8631)
- Non-unique keys may now cause children to be duplicated and/or omitted. Using non-unique keys is not (and has never been) supported, but previously it was a hard error.
- Shallow renderer no longer calls componentDidUpdate() because DOM refs are not available. This also makes it consistent with componentDidMount() (which does not get called in previous versions either).
- Shallow renderer does not implement unstable_batchedUpdates() anymore.
- ReactDOM.unstable_batchedUpdates now only takes one extra argument after the callback.
The names and paths to the single-file browser builds have changed to emphasize the difference between development and production builds. For example:
- react/dist/react.js → react/umd/react.development.js
- react/dist/react.min.js → react/umd/react.production.min.js
- react-dom/dist/react-dom.js → react-dom/umd/react-dom.development.js
- react-dom/dist/react-dom.min.js → react-dom/umd/react-dom.production.min.js

The server renderer has been completely rewritten, with some improvements:
- Server rendering does not use markup validation anymore, and instead tries its best to attach to existing DOM, warning about inconsistencies. It also doesn't use comments for empty components and data-reactid attributes on each node anymore.
- Hydrating a server rendered container now has an explicit API. Use ReactDOM.hydrate instead of ReactDOM.render if you're reviving server rendered HTML. Keep using ReactDOM.render if you're just doing client-side rendering.
When "unknown" props are passed to DOM components, for valid values, React will now render them in the DOM. See this post for more details. (@nhunzaker in #10385, 10564, #10495 and others)
Errors in the render and lifecycle methods now unmount the component tree by default. To prevent this, add error boundaries to the appropriate places in the UI.

react-dom

16.0.0

16.0.0 (September 26, 2017)

New JS Environment Requirements

New Features

16.0.0

16.0.0 (September 26, 2017)

New JS Environment Requirements

New Features

Breaking Changes

Removed Deprecations

16.0.0#

16.0.0 (September 26, 2017)

New JS Environment Requirements

New Features

16.0.0#

16.0.0 (September 26, 2017)

New JS Environment Requirements

New Features

Breaking Changes

Removed Deprecations

16.0.0

16.0.0