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: use console.createTask
to improve traces where supported
#69
Conversation
Codecov Report
@@ Coverage Diff @@
## main #69 +/- ##
==========================================
- Coverage 97.63% 96.24% -1.40%
==========================================
Files 5 5
Lines 466 506 +40
Branches 98 106 +8
==========================================
+ Hits 455 487 +32
- Misses 11 19 +8
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
More info: https://developer.chrome.com/blog/devtools-modern-web-debugging/#linked-stack-traces
This has relatively low support at the moment outside of Chromium browsers. Node support is available in Node 19+: nodejs/node#44792.
However, it is a very nice DX improvement where supported.
Note that the remaining anonymous functions in the stack trace will be named if/when #68 merges.