~/talk

OUTBREAK: index-sw-9a4c43b4b4778e7d1ca619eaaf5ac1db.js

Talkat JS Kongress 2017 · on Tuesday, 2017-11-14· [web-platform, devops-and-delivery]
slides:none on file

A concrete failure story: a broken service worker (due to missing cache API in some browsers and an uncaught install error) becomes permanently installed on a subset of clients, producing over 2,000 errors in 24 hours and surviving attempts to push updates. The talk shows the exact APIs involved (Cache, fetch, clients, importScripts, IndexedDB), tooling and fixes used (SW tester and SW Toolchain, async/await plus Babel/uglify), mitigation patterns (feature flag / kill switch, noop worker, importScripts versioning) and that many devices still remain infected despite rolling fixes.

AI-written summary · about

  1. 0:00Start
  2. 9:35WHAT THE HELL IS SERVICEWORKER?
  3. 13:12DELAY SERVICEWORKER REGISTRATION
  4. 13:32KNOW YOUR DEPENDENCIES
  5. 14:11CACHE SMARTER
  6. 15:24USE A LIBRARY FOR MESSAGING
  7. 16:06SET CORRECT CACHE HEADERS
  8. 17:02ADD A FEATURE FLAG/KILL SWITCH
  9. 17:33DON'T CACHE BAD RESPONSES
  10. 18:20GUARD AGAINST MISSING APIS
  11. 18:42TEST YOUR SERVICEWORKER
  12. 20:11USE A SERVICEWORKER GENERATOR TOOL
~/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.