Error overlay is shown, even when there's an error boundary

[Janpot]

Verify canary release

• I verified that the issue exists in Next.js canary release

Provide environment information

Reproduction in the following sandbox: https://codesandbox.io/s/unruffled-darkness-2xqhi1?file=/pages/index.js

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

When an error is thrown in a component that is rendered under an error boundary, the Next.js error overlay is displayed, even though the error is handled. Showing the overlay is very disruptive and a false alarm.

Expected Behavior

No overlay is shown

To Reproduce

Open the code sandbox and click the button.

[timneutkens]

This is intentional as per facebook/create-react-app#6530 (comment)

[Janpot]

That's a curious line of reasoning. It's like saying "hey, we're going to ignore your try/catch statements just in case you didn't intentionally put them there".

Doesn't suspense for data fetching rely heavily on error boundaries? How will this ever play nice with error overlay?

[jankaifer]

Since this is not really next.js specific, I'll close this as a duplicate of facebook/create-react-app#6530

EDIT: my bad it's not the react repo but CRA.

[jankaifer]

Either way, this is not a bug and we think it is the right thing to do.
As Dan said in facebook/create-react-app#6530 (comment)

I'll move this into discussions where we can discuss if there are some valid use-cases that would benefit from this.

[wfl-junior]

How can I at least opt out of showing error overlays for errors that are caught by an ErrorBoundary?

[imclint21]

Any news on this? This modal is really disturbing when we want to catch errors with error boundaries.