Kicking Bugs and Logging Names: Errors in JavaScript Error Reporting

on YouTube ↗23m

" summary

History of window.onerror includes adding column and an error object around 2013 but the error.stack value is a nonstandard string so each browser needs custom parsing; cross origin issues require Access-Control-Allow-Origin plus crossorigin on script tags to turn "Script error" into real stacks; minification pushes use of source maps; common solutions include tres kit and stacktrace j/s and SDK instrumentation like century that parses stacks and ships errors in the background so reporting actually works.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 3:02debug output
3. 4:49Breakpoints
4. 12:06Same-Origin Policy

" related talks

• 27mTraces of Errors: Getting Better JavaScript StacktracesTodd H. Gardner · MountainWest JavaScript 2014
• 40mManeuvering Errors within the Bowels of JavaScriptBret Little · UtahJS Conf 2017
• 27mGetting the Most out of JavaScript ErrorsBen Vinegar · Node+JS Interactive 2019
• 58mSquashing JavaScript bugsTodd H. Gardner · NDC London 2017
• 01h 04mJavaScript's Most WantedTodd H. Gardner · NDC Sydney 2016
• 32mExpect the Unexpected: How to Deal with Errors in Large Web ApplicationsMats Bryntse · TestCon Vilnius 2018
• 20mImproving the process of debugging JavaScript errorsFinbar Fleming · Conf42 JavaScript 2022
• 16mHarden up your ajax!Alex Mackey · Web Directions Code 2014