Joe Haddad

I think this is important enough to not tag as a future idea and instead for 0.10. 😄

What if the error overlay didn't take up the full screen and appeared as a intuitively dismissible modal instead? This is the best balance IMO: - You can see that...

I'm not convinced it'd be a DX win to see no overlay whatsoever for an unhandled error in your application. I guess this could become more annoying if you're leveraging...

Personally, I consider an error boundary being triggered an unhandled error: your component tree crashed (notwithstanding experimental features). I can see how opinions would differ here, though. How would you...

This is now released. 😄

Reverted due to a bug in webpack.

There's no prior art, but I'd love to see a solution that scales. We're on board with this configuration but would like to discuss its ergonomics first.

I think we'd rather use a file. e.g. ```js // react-app.config.js module.exports = { workbox(options) { // should options be frozen? return options } }; ```