-
Notifications
You must be signed in to change notification settings - Fork 178
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
feat: support report error cause
#308
base: main
Are you sure you want to change the base?
Conversation
cause
Hi, @pi0 ~ What's your thought of this feature? Looking forward to your reply. 🫡 |
This would be so good to have! The cause adds important context in many errors (e.g. fetch errors with undici). Also the name/type of the error (e.g. "TypeError: ") gets lost with consola. |
@ pi0 Could you let me know any progress of this feat? Looking forward to ur thought~ 😂 |
@kongmoumou it is on my list sorry got delayed (i might need to push small refactors before) |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #308 +/- ##
===========================================
- Coverage 61.08% 22.11% -38.98%
===========================================
Files 13 42 +29
Lines 1380 2180 +800
Branches 58 87 +29
===========================================
- Hits 843 482 -361
- Misses 537 1671 +1134
- Partials 0 27 +27 ☔ View full report in Codecov by Sentry. |
The
cause
property of Error had been support in most runtime and been widely adapted by many repo.The Chrome devtool already support showing caused error like screenshot below ⬇️
This PR support report error cause to console while used in node. Related issue #202
Test code provided: