Sending your Angular App into deep, deep offline with Workbox
summary
Claim is concrete: use Workbox to produce a custom service worker that precaches an application shell, handles runtime caching strategies, and queues API writes for delivery when connectivity returns. The build uses workbox-build’s injectManifest to inject a hashed precache list, bundles the worker with Rollup to tree-shake and minify, and wires update signals via broadcastUpdate / workbox-window plus background sync for deferred posts. This replaces Angular Service Worker when full control and advanced runtime logic are required; iOS background sync remains unsupported.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:38Maxim Salnikov
- 2:46What is PWA at all?
- 10:34Let's build an App shell
- 14:36Angular Service Worker
- 17:04Working modes
- 18:49Build script configuration
- 19:30Source service worker
- 20:34Precaching manifest
- 20:58Build flow integration
- 22:35Option #1: BroadcastChannel
- 23:24Option #2: Service worker lifecycle
- 25:36Was service worker file updated?
- 27:19Routes and strategies
- 31:48Deploying only what we use
- 33:03Using bundler
- 33:16Needed plugins
related talks
47mSending the Angular app into deep, deep offline with Workbox
32mBuilding an Angular PWA Angular Service Worker or Workbox?
58mOffline Second
54mBuilding an Angular PWA: Angular Service Worker or Workbox?
51mAutomating a service worker with Workbox 6
17mHow to build a PWA and stay sane: Introduction to Workbox
01h 00mProgressive Web Apps with Angular: Tips for Advanced Users
38mAutomating Service Workers with Workbox 6