dio.js - npm Package Versions

8.0.3 (09 October 2017)

• patch error when used with brunch, fusebox and browserfy bundlers.

8.0.2 (08 October 2017)

• reflect setState calls from componentWillReceiveProps lifecycle to update state synchronously like React.

8.0.1 (06 October 2017)

• patch dio.version to reflect the right version.

8.0.0 (06 October 2017)

Overview

• Support componentDidCatch.
• Support stateful functional components.
• Support rendering fragments.
• Support rendering Iterables.
• Support EventListener interface.
• Support context, getChildContext.
• Support strings refs for functional components.
• Support an opaque data-structure for props.children
• Support mounting to top-level html element.
• Support out of order server side rendering with portals.
• Adds top-level API createPortal.
• Adds top-level API findDOMNode.
• Adds top-level API hydrate.
• Adds top-level API Children.
• Adds top-level API unmountComponentAtNode
• Adds invarient errors for render if target container is invalid.

Breaking Changes.

• componentDidThrow is renamed to componentDidCatch and unmounts the DOM if an error state is left unhandled. However errors coming from event handlers are exluded from this behaviour.

• props.children is now an opaque data-structure, which might break your application if you relied on it always being of an Array type.

• Passing an invalid object to #render as the container to render to will throw an error. Falsey values are not considered invalid values, these will fallback to the root Node in a DOM tree. Truethy values that are not of or do not extend/mimic the native Node class of the platform would be considered invalid.

• Hydration now exists soley as an explicit API hydrate.

• Hydration will now always try to make sure the DOM matches the virtual elements generated on the client. This may result in removing nodes or adding DOM nodes. This only bears any meaning if the server and client renders do not match in which case the reconciler will always try to make the DOM match what you render on the client.