Now that I use #Rollup to generate my Service Worker with #Workbox in #Eleventy, I guess I should try to remove #Webpack from #JavaScript assets bundling… 😅
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
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
Inspired by @5t3ph's 11ty-sass-skeleton, my own Pack11ty #Eleventy template project now uses Dart Sass CLI and a few postcss plugins for Sass instead of the previous unnatural Rollup configuration.
Ok, time to really say goodbye to Application Cache…
4 years and a half after opening, this issue for my game #esviji is now closed! 🎉
https://github.com/esviji/esviji/issues/101#issuecomment-617440727
Thanks to #Workbox and #Rollup, it's been easier than I feared. 🙏
Oh… and I also moved to #Netlify … 😁
Want to play? Let's play!
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… 😥