Unhandled rejections and other awaited promise tales
summary
Concrete claims and actions matter: Node Core adds a runtime flag that turns unhandled rejections into exceptions, V8 and Node 12 expose async stack traces (zero-cost) so the origin of awaited errors is visible, and several core APIs gain native promise variants (file system, DNS, events) instead of ad hoc wrappers. The talk demonstrates async/await refactors, explains why unhandled promise accumulation keeps processes running, and shows that the flag and native APIs actually land and make error handling and observability work better.
AI-written summary · about
chapters (8)
- 0:00Rejections and promises
- 2:52Promises as language feature
- 8:13Async/await implications
- 11:20Unhandled rejections in Node.js
- 14:09Proper rejection handling
- 16:36Async stack traces in Chrome
- 17:17Node.js native promises
- 18:44Future improvements
related talks
57mError handling: doing it right!
28mError handling: doing it right!
20mPromises API in Node.js Core: Part "Do", the Update!
14mThe Promised Path to Async, Awaits
32mError handling: doing it right!
24mFinding Broken Promises in Asynchronous JavaScript Programs
23mHolding on to Your Performance Promises
21mPromises API in Node.js core: where we are and where we’ll get to
