Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: include stack in browser uncaught error reporting #5107

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

JoshuaKGoldberg
Copy link
Member

@JoshuaKGoldberg JoshuaKGoldberg commented Feb 28, 2024

PR Checklist

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 peter@cornerstonenw.com

browser-entry.js Outdated Show resolved Hide resolved
@coveralls
Copy link

coveralls commented Feb 28, 2024

Coverage Status

coverage: 94.359%. remained the same
when pulling adc04cb on JoshuaKGoldberg:browser-uncaught-errors
into 3735873 on mochajs:master.

@prust
Copy link
Contributor

prust commented Feb 29, 2024

thanks @JoshuaKGoldberg!

@JoshuaKGoldberg
Copy link
Member Author

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

@JoshuaKGoldberg
Copy link
Member Author

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

@JoshuaKGoldberg JoshuaKGoldberg restored the browser-uncaught-errors branch March 5, 2024 12:33
@JoshuaKGoldberg JoshuaKGoldberg added the run-browser-test run browser tests on forked PR if code is safe label Mar 12, 2024
@github-actions github-actions bot removed the run-browser-test run browser tests on forked PR if code is safe label Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

🐛 Bug: Browser doesn't include call stack for global uncaught errors
3 participants