Stacktraces, Sourcemaps & Everything In Between
summary
Walks through exact source map JSON fields and VLQ mappings, shows decoding by binary search to map bundle column 2700 back to original file and column, and warns never to ship maps after citing an Apple leak, a 60 MB Cloud Code map, and a discovered Stripe key tied to a $1.76M account with a $95k bounty. Describes deterministic debug ID UUIDs injected at build time, bundler plugins that upload and then delete maps, and Turbopack support that drastically reduces build+upload time and fixes pairing failures.
AI-written summary · about
chapters (12)
- 0:00Introduction and setup
- 1:05Stack traces basics
- 4:59What are source maps
- 7:06Source map structure
- 9:10VLQ encoding explained
- 13:26How browsers use source maps
- 14:11Bundler source map options
- 16:39Pairing errors with source maps
- 18:44Debug IDs solution
- 21:52Debug IDs standardization
- 22:12Challenges with source maps
- 23:19Future improvements
related talks
30mA deep dive into Source Maps
24mSource maps through the looking glass
40mJavaScript Source Maps, can we do better?
12mSource maps for debugging
40mAll you Need to Know About Xcode Hidden Logs
46mUsing LLDB, Instruments, and Xcode to understand a codebase
42mDissecting Ruby with Ruby
46mThe Hidden Secrets of Debugging