~/talk

Error handling: doing it right!

Talkat JSCamp Barcelona 2019 · 2019-07-18..07-19· [nodejs, developer-experience]
slides:none on file

Shows concrete fixes: create a shared application Error class with user-facing subclasses and status codes, log everything, and let most errors bubble to a single layer. Recommends async/await for meaningful V8 stack traces, use util.promisify instead of manual Promise constructors, retry outgoing requests (example: up to 10 tries for flaky Facebook API calls), and enable Node’s --unhandled-rejections / multiple resolve hooks to catch swallowed promise bugs.

AI-written summary · about

  1. 0:00Start
  2. 13:17Unhandled rejections
  3. 18:17Error classes
  4. 19:04Error handler layers
  5. 25:07util.promisify
  6. 25:37unhandled-rejections
  7. 30:09Summary / Rules
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.