Expect the Unexpected: How to Deal with Errors in Large Web Applications
summary
Shows how to implement real error monitoring for large JavaScript frontends: a tiny client logger (three lines of JS) sends stack and user context to a backend, adding crossorigin to script tags removes cryptic "Script error", and session replay with html2canvas plus recording of clicks produces a replayable session that exports into Siesta tests. The pipeline reproduces a real split‑task bug, automates regression tests, and lets teams fix and verify deployments quickly.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:49What are JavaScript errors
- 4:00The cryptic script error message
- 7:32How to build your own error logger
- 10:37How to deal with bugs
- 14:24Enterprise email pingpong
- 17:11Whos doing the ostrich
- 19:50Second generation tools
- 21:52Automation
- 28:30Crash Report
- 29:02Technical Stuff
- 30:10Privacy concerns
- 30:46Recap
related talks
53mObservable Web Applications
12mSolve 100% of your errors
08mMonitoring Errors and Slowdowns with a JS Frontend and Node Backend
22mFrontend Observability Odyssey
08mMonitoring Errors and Slowdowns Across JS Applications
27mTraces of Errors: Getting Better JavaScript Stacktraces
16mHarden up your ajax!
27mGetting the Most out of JavaScript Errors