Given
```js
function ThrowInEffect() {
  React.useEffect(() => {
    throw new Error('passive effect')
  }, [])
  return null;
}
```

In React 17 this error got logged to the console (and triggered the error overlay in create-react-app) regardless of whether `ThrowInEffect` was a child of an Error Boundary or not.

In React 18 (`createRoot` and legacy root API) an Error Boundary will prevent logging that error to the console (and not trigger the error overlay in create-react-app).

Errors during render work like they did in React 17.

Behavior in React 17: https://codesandbox.io/s/react-17-error-boundaries-vp21e?file=/src/index.js
Behavior in React 18: https://codesandbox.io/s/react-18-error-boundaries-psd56?file=/src/index.js


Recording of effect errors in React 17 and 18 and with and without Error Boundaries_

https://user-images.githubusercontent.com/12292047/122749780-053ced00-d28e-11eb-98ce-075dcdc53ee2.mp4


'This unit of work tag should not have side-effects. This error is ' +
            'likely caused by a bug in React. Please file an issue.',
        );
    }
  }
  if (enableScopeAPI) {
    
    
    if (finishedWork.flags & Ref && finishedWork.tag !== ScopeComponent) {
      commitAttachRef(finishedWork);
    }
  } else {
    if (finishedWork.flags & Ref) {
      commitAttachRef(finishedWork);
    }
  }
}
function hideOrUnhideAllChildren(finishedWork, isHidden) {
  
  const isModernRoot = (finishedWork.mode & ConcurrentMode) !== NoMode;
  const current = finishedWork.alternate;
  const wasHidden = current !== null && current.memoizedState !== null;
  
  let hostSubtreeRoot = null;
  if (supportsMutation) {
    
    
    let node: Fiber = finishedWork;
    while (true) {
      if (node.tag === HostComponent) {