feat: error integration

[pmmmwh]

After a few nights of hard work this is finally presentable 🎉

There are still a lot of things that are missing here: no custom error overlays, no ways to disable the integration, no support for proxies, etc. Those will come later - I think it is more important for us to get the general DX right.

Please feel free to use this PR to track/iterate on changes that have to be made.

(Side note: I am debating to split the error overlay into a separate package/refactor with React, but didn't want to add build steps and mono-repo infra to this tiny plugin repo just yet)

@bvaughn @gaearon
Please test out the branch and comment on the DX 🙇

CC @charrondev @maisano - Since you two have adopted the concept early. I would be happy if you can try this out in real projects too.

[pmmmwh]

we can scan source code after modules are built and detect traces of the plugin's work

Maybe you can inject a module that you'd expect the Babel plugin to "catch" with a RefreshReg call, and then verify that.

Implemented this idea as the default option with an escape hatch to disable the check just in case the user is doing something exotic.

Moving on to tweaking the layout of the overlay.

[gaearon]

Getting Error: Cannot find module './runtime/TestComponent.js' on this branch

[pmmmwh]

Getting Error: Cannot find module './runtime/TestComponent.js' on this branch

Fixed. I broke something after stashing, sorry.

[gaearon]

Is it worth keeping it in a branch / unreleased at this point? Might be easier to test outside of this repo.

[pmmmwh]

Is it worth keeping it in a branch / unreleased at this point? Might be easier to test outside of this repo.

Maybe I'll merge this first, then release it under my scope so that the world can test it?

[gaearon]

Sure

[pmmmwh]

Did some last minute bug fixes and remodeled some parts of the overlay.

Time to merge this to release v0.1.0 and watch the world crumble 🎉