Opt out of next.js `componentDidCatch`

Feature request

Is your feature request related to a problem? Please describe.

I want to have errors thrown in development so I can use the chrome debugger’s pause on exceptions and inspect the error’s environment. The current error rendering provided by next.js swallows the exception and is a lot less useful than chrome’s debugger.

Describe the solution you’d like

Throwing an error in a custom _app.js causes the error to be caught by some parent component (I think AppContainer?) Maybe a solution is to stop catching errors if we implement a componentDidCatch in App.js

Describe alternatives you’ve considered

Being a better programmer. (💩 impossible for me tho 💩)

Additional context

Pls. Stop catching my errors when you don’t even catch them in production 😭😭😭 The devtools feature I’m talking about

[timneutkens]

I mean, you could add debugger; in componentDidCatch https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/debugger

Anyway we’re planning to remove react-hot-loader soon.

[brainkim]

Update for 6.1. Hot reloading is much nicer! 🎉🎷🎊🥁 Unfortunately, errors in the render path seem to make the page to become unresponsive (devtools can’t be opened, page is not interactive, page will not load on full reload). Not sure if this is better but thanks for your efforts. Let me know if you want me to create a new issue for this.