Maneuvering Errors Within the Bowels of JavaScript
summary
Examines how JavaScript asynchronous control flow corrupts and accumulates errors—showing concrete bad patterns such as lost stacks from nested callbacks and swallowed Promise rejections. Reproduces the problem with instrumentation, then fixes it by using Promises/async‑await and explicit throw/return propagation, and shows how Angular digest cycles can hide or duplicate failures with a minimal repro and code changes that restore meaningful stack traces.
AI-written summary · about
chapters (9)
- 0:00JavaScript error handling
- 2:00Error debates
- 5:16Spring and React errors
- 8:59Progressive error strategies
- 13:13JavaScript error causes
- 17:22Production functions and time
- 20:19Dev vs prod errors
- 24:02Code errors
- 26:26Web error handling
related talks
40mManeuvering Errors within the Bowels of JavaScript
25mDebugging async JS
22mHave You Heard the Joke About Async Debugging? I Promise It Is Good
25mKablooie: A History of Errors & a Future of Solutions
01h 14mJavaScript the Grumpy Parts
27mTraces of Errors: Getting Better JavaScript Stacktraces
26mNow and .then: Debugging Async JS
46mAsynchronous JS Without the Cringe