capture uncaught exceptions in aws-lambda

[djskinner]

Goal

AWS add a default unhandledRejection listener that forcefully exits the process. To workaround this the aws-lambda plugin removes all the listeners and only runs them after our own unhandled rejection handler has run.

It turns out the same thing is happening with uncaught exceptions but we weren't handling that case. This PR adds support for uncaught exceptions in the same manner as unhandled rejections.

To be clear the aws-lambda plugin previously was not reporting any errors that were caught by node's global uncaught exception handler. This PR fixes that.

Design

• Same approach as used for unhandled rejections

Changeset

Testing

• e2e test was added covering this case
• Verified locally using aws sam

[github-actions]

@bugsnag/browser bundle size diff

	Minified	Minfied + Gzipped
Before	44.63 kB	13.64 kB
After	44.63 kB	13.64 kB
±	No change	No change

code coverage diff

<temporarily disabled>

Generated by 🚫 dangerJS against eda4675

[djskinner]

The domain error handler was (incorrectly) preventing the application from crashing and returning a response. Now, the exception goes to the top-level uncaught exception handler before the process exists as it should

[imjoehaines]

Suggested change

	process.on('uncaughtException', async (reason, promise) => {
	for (const listener of listeners) {
	await listener.call(process, reason, promise)
	}
	process.on('uncaughtException', async (err, origin) => {
	for (const listener of listeners) {
	await listener.call(process, err, origin)
	}