errors anywhere in their child component tree, log those errors, and display a fallback UI instead of the crashed component tree. Fallback UI card for a component that fails to render and get’s catched inside componentDidCatch
some other DOM heirarchy A typical use case for portals is when a parent component has an overflow: hidden or z-index style, but you need the child to visually “break out” of its container. For example, dialogs, hovercards, and tooltips.
portal will propagate to ancestors in the containing React tree, even if those elements are not ancestors in the DOM tree. ➔ A Parent component in #app-root would be able to catch an uncaught, bubbling event from the sibling node #modal-root.
server than React 15 ➢ render() becomes hydrate() ➢ More efficient html ➢ Less Strict Client Side Checking ➢ Doesn’t need to be compiled for best performance