OUTBREAK: index-sw-9a4c43b4b4778e7d1ca619eaaf5ac1db.js
summary
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
chapters (12)
- 0:00Start
- 9:35WHAT THE HELL IS SERVICEWORKER?
- 13:12DELAY SERVICEWORKER REGISTRATION
- 13:32KNOW YOUR DEPENDENCIES
- 14:11CACHE SMARTER
- 15:24USE A LIBRARY FOR MESSAGING
- 16:06SET CORRECT CACHE HEADERS
- 17:02ADD A FEATURE FLAG/KILL SWITCH
- 17:33DON'T CACHE BAD RESPONSES
- 18:20GUARD AGAINST MISSING APIS
- 18:42TEST YOUR SERVICEWORKER
- 20:11USE A SERVICEWORKER GENERATOR TOOL
related talks
25mOutbreak: index-sw-9a4c43b4b4778e7d1ca619eaaf5ac1db.js
25mOUTBREAK: index-sw-9a4c43b4b4778e7d1ca619eaaf5ac1db.js
30mWeb Service Workers - Breaking The Web Because It Would Be A Sh...
42mHow Do Service Workers Even?
30mThe Beauty of Service Workers
43mService workers
01h 00mService Worker: Bringing Native App Experience to Web Apps
35mTame your service worker [...]
