https:/
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 text editor with shared cursors. Adding in
yjs-indexeddbmade it work offline. This was all mostly out of the box, with very little setup; the degree to which everything Just Works is impressive.
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
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…
Tried to write a fresh new Service Worker with #Workbox 5 and #Rollup (first time ever), almost copy/pasted from what @jeffposnick did in https://github.com/GoogleChromeLabs/so-pwa but I get a strange error reporting mixed content… 😥
Martin Kleppmann, Adam Wiggins, Peter van Hardenberg and Mark McGranaghan
I talk a lot about POSSE these days, but it's mainly about content, not applications. For them, it is often difficult to host a solution yourself,…
How much data should my Service Worker put upfront in the offline cache?
I love when Web site/apps work even when I'm offline. I've made my SVG game esviji work offline thanks to appcache just after attending Jake Archibald conference about why Application Cache is a Douchebag during the 2012 edition of the Paris Web conference. Fortunately, we have now Service Workers (in some browsers), which gives us more control over this kind of cache for offline browsing. But as Uncle Ben says, “With Great Power Comes Great Responsibility”.
Jake Lazaroff 
Jeff Posnick