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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 Bug: Browser doesn't include call stack for global uncaught errors #5106
Open
4 tasks done
Labels
area: browser
browser-specific
status: accepting prs
Mocha can use your help with this one!
type: bug
a defect, confirmed by a maintainer
Comments
JoshuaKGoldberg
added
type: bug
a defect, confirmed by a maintainer
area: browser
browser-specific
status: accepting prs
Mocha can use your help with this one!
labels
Feb 28, 2024
This was referenced Feb 28, 2024
Closed
Closed
Ah that's nifty to hear you're using Mocha in the Chrome DevTools! We're just waiting for review from another maintainer on #5107. I know everyone else has been swamped lately, so unclear when we'll be able to. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: browser
browser-specific
status: accepting prs
Mocha can use your help with this one!
type: bug
a defect, confirmed by a maintainer
Bug Report Checklist
faq
label, but none matched my issue.Expected
When an uncaught error occurs during a test in browsers, you'd expect to see the call stack. That's useful.
Actual
Mocha's browser error handling code was written before browsers gave nice stacks (eb58761).
Minimal, Reproducible Example
Using a minimal browser setup such as in mochajs/mocha-examples#72:
Versions
Mocha: 10.3.0
Additional Info
This was filed long ago in #2167, then a fix proposed in #3952. Since #2167 is quite old, re-filing to be more current.
The text was updated successfully, but these errors were encountered: