https://nodejs.org/api/process.html#event-uncaughtexceptionmonitor

• process.on("unhandledRejection", cb)
• process.on("unhandledException", cb)
• process.on("uncaughtExceptionMonitor", cb)
• process.setUncaughtExceptionCaptureCallback(cb)

This lets Sentry get error reporting working.

Ideally, the fix would go here:

We would add an unhandled rejection scope for either rejections or exceptions and have some way to distinguish between the two. This one would call into JS potentially for multiple handlers. The part that gets a little tricky is in unit tests where we rely on this behavior for expect().toThrow()

cc @dcramer