~/talk

Improving the process of debugging JavaScript errors

Talkat Conf42 JavaScript 2022 · on Thursday, 2022-11-17· [javascript, web-performance]
slides:none on file

Production JavaScript errors get captured by an SDK that sends fingerprinted stack traces and page telemetry to a monitoring platform, enabling immediate grouping, alerting and triage. Real customers report setup in 30–60 minute setup and rapid ROI: one user drops from 40,000 → 2,000 errors in six weeks. Metrics show developers spend up to 10–15 hours weekly on bugs, so adding Rollbar SDK and phased workflows (install, triage, notify, enrich, automate) cuts user impact and developer debugging time.

AI-written summary · about

  1. 0:00Debugging JavaScript errors
  2. 1:40Speaker intro & Rollbar
  3. 4:29Cost of errors
  4. 6:33JS debugging challenges
  5. 9:19Logging vs error monitoring
  6. 11:28JS errors lifecycle
  7. 13:57Error monitoring benefits
  8. 15:21Error monitoring adoption
  9. 17:05Call to action
~/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.