fix: include stack in browser uncaught error reporting

[JoshuaKGoldberg]

PR Checklist

• Addresses an existing open issue: fixes 🐛 Bug: Browser doesn't include call stack for global uncaught errors #5106
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

Continues #3952. In summary, this change uses the "newly" available err parameter in onerror to log a nicer stack.

Co-authored-by: Peter Rust [email protected]

[coveralls]

coverage: 94.359%. remained the same
when pulling e1aa60d on JoshuaKGoldberg:browser-uncaught-errors
into 2f3fedc on mochajs:master.

[prust]

thanks @JoshuaKGoldberg!

[JoshuaKGoldberg]

I hadn't noticed that #5080 did this same thing. Closing in favor of that one. 🚀

[JoshuaKGoldberg]

...and, re-opening per #5080 (comment). 😄

[voxpelli]

We should go through all the browser polyfilling eventually, but this looks good, only the sinon fix needed.

---

For future reference / personal reference: Related APIs:

• https://developer.mozilla.org/en-US/docs/Web/API/Window/error_event
• https://nodejs.org/api/process.html#event-uncaughtexception

Could perhaps want to move Mocha to this one eventually:

• https://nodejs.org/api/process.html#processsetuncaughtexceptioncapturecallbackfn

[JoshuaKGoldberg]

This was released in [email protected]. 🚀