Outbreak: index-sw-9a4c43b4b4778e7d1ca619eaaf5ac1db.js
summary
A deployment typo triggers a cascade that turns ServiceWorkers into persistent zombies, infecting tens of thousands of clients; most recover but a stubborn minority remains cursed despite attempts to unregister. The talk gives concrete diagnostics (a swallowed install promise), practical defenses (cache-versioning, feature flags), tooling and tests — sw-test-env mock and kill switch/no-op service worker — and a postmortem showing what was built, how it failed, and which fixes actually work.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 6:45A horror story
- 10:10What is a Service Worker
- 11:59AsyncAwait
- 12:47AsyncGenerator
- 13:07Dont Register
- 13:28Know your dependencies
- 14:05Cache smarter
- 14:58Avoid forcing activation
- 15:48Never rename the Service Worker file
- 16:21Set correct cache headers
- 17:12Invalidation
- 17:37FeatureFlagKillSwitch
- 18:12Dont Cache
- 19:09Guard Against Missing API
- 19:33Test Your Service Worker
- 20:52SWTestEnd
- 21:17UnitTest
- 22:11Recipe
- 22:29Mystery
- 23:05Conclusion
related talks
23mOUTBREAK: index-sw-9a4c43b4b4778e7d1ca619eaaf5ac1db.js
35mTame your service worker [...]
51mAutomating a service worker with Workbox 6
33mService Workers
27mAnd Now You Understand Service Workers
05mLightning talk: Service Workers, use them
43mService workers
42mService Worker: Taking the Best From the Past Experience for The Bright Future of PWAs