Angular and Service Workers
summary
Angular IO uses Service Workers to serve a production build offline and hit a Lighthouse 100 PWA benchmark by registering a generated ngsw-manifest and shipping the package @angular/service-worker. The lifecycle is install → activate → fetch; install precaches static files, fetch uses cache-first with network fallback (clone streams before caching), and activate cleans old caches. Angular CLI flips service worker on in angular.json, supports external assets, route redirection for SPA routes, and configurable dynamic caching strategies.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 2:11Angular and service workers overview
- 7:28Service worker fundamentals
- 17:47Service worker lifecycle and caching
- 21:16Angular service worker features
- 25:37Demo of offline Angular app
- 30:58Dynamic content and routing
- 32:04Q&A and acknowledgments
related talks
36mAngular and Service Workers
24mBuild progressive web apps with Angular
54mBuilding an Angular PWA: Angular Service Worker or Workbox?
43mAutomatic Progressive Web Apps using the Angular Mobile Toolkit
32mBuilding an Angular PWA Angular Service Worker or Workbox?
37mAngular PWA: crafting apps that adapt anywhere
22mAutomatic Progressive Web Apps using Angular Service Worker
41mPerformant and Accessible Angular Apps as PWAs
