A year of other’s bugs: the sad state of error handling
summary
Error handling in JavaScript is concretely broken for newcomers: tiny typos and type confusions cause hours of debugging, exemplified by errors like PI.push is not a function and cannot read property add of undefined, and platform messages such as EADDRINUSE or “unexpected token in JSON at position 0.” The ecosystem uses Heroku, Node/Express, webpack, React and Elm; Elm’s verbose error UI and Chrome’s audits panel actually help, while a quick GitHub search finds one million issues revealing widespread neglect. File issues, add context, and surface actionable fixes.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:19Mixing Up Array and Object Prototype Methods
- 10:56Why Is Error Handling So Bad
- 12:17Writing Error Messages for Ourselves
- 16:54Types of Error Objects
- 27:24Elegant Solutions
- 29:12Audits Panel
related talks
42mBugs We Love
22mYes, Your Error Messages Can Be Beautiful And Developers Can Love Them
32mError handling: doing it right!
38mJavascript Considered...Useful
31mHow Many Ways to Say I'm Sorry, Error Handling in React
28mError handling: doing it right!
58mSquashing JavaScript bugs
50mFrontend Development 2018 - What's in your stack?