Traces of Errors: Getting Better JavaScript Stacktraces

on YouTube ↗27m

" summary

Shows that browsers disagree about Error internals (Chrome embeds stack, IE only generates it on throw, Firefox exposes file/line/column) and that anonymous callbacks erase call-site names, so debugging is hard. Demonstrates a working monkey-patched addEventListener that forwards exceptions back into app-level handlers (adds extra stack frames but restores visibility), cites StackTrace.js, TraceKit, ZoneJS, trackjs as tools, and notes it took about 15 years for browsers to pass full stacks to global handlers.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 0:26Traces of Errors Getting Better JavaScript Stacktraces
3. 4:02Demo JavaScript Error
4. 11:361. {object Error} 2. Error Paths
5. 20:45Demo Error Paths callback edition

" related talks

• 27mGetting the Most out of JavaScript ErrorsBen Vinegar · Node+JS Interactive 2019
• 58mSquashing JavaScript bugsTodd H. Gardner · NDC London 2017
• 26mThe Trouble with TracersThomas Watson · NodeConf.EU 2019
• 23mKicking Bugs and Logging Names: Errors in JavaScript Error ReportingLiz Krane · ReactiveConf 2019
• 29mEssential JavaScript debugging tools for the modern detectiveRebecca Hill · JSConf Budapest 2019
• 33mEssential JavaScript debugging tools for the modern detectiveRebecca Hill · You Gotta Love Frontend 2019
• 40mManeuvering Errors within the Bowels of JavaScriptBret Little · UtahJS Conf 2017
• 01h 04mJavaScript's Most WantedTodd H. Gardner · NDC Sydney 2016