Who still thinks writing a Service Worker for basic features (performance with cache, offline fallback) is cumbersome?
Using #Workbox recipes make it so easy!
Here's the Service Worker for https://pack11ty.dev 😍
https://github.com/nhoizey/pack11ty/blob/main/src/assets/js/service-worker.js
It helps a lot that various libraries in the ecosystem compose well. Just snapping together ProseMirror, Yjs and Y-Sweet gave me a collaborative rich…
If someone is creating service workers with #Workbox recipes and injectManifest, a build with #esbuild, and doesn't have any issues, I'm interested! 😅
I have a very strange issue:
https://github.com/GoogleChrome/workbox/issues/3207
Bonus points if this is with #Eleventy
Is it ok to use Workbox's injectManifest with the recent recipes warmCache option?
I tried this without success in the Service Worker in Pack11ty:
Jake Lazaroff
staticResourceCache({
warmCache: self.__WB_MANIFEST,
});Other caches are warmed up, not this one.
How do you test a service worker, anyway?
if you're writing a service worker from scratch, if you're using one of Workbox's more exotic plugins or custom strategies, or if your service worker's…
Looks like #Workbox 6 will improve a few things I struggled with in the past, it became so easy to develop great Web Services! 👍
https://github.com/GoogleChrome/workbox/releases/tag/v6.0.0-alpha.1
Jeff Posnick