Jeff Posnick

@tconroy—apologies for not having found a chance to respond to this yet. It's still on my radar, but it's going to require a bit of investigation to familiarize myself with...

I'm not sure how comprehensive this answer is going to be, because there's a lot of different pending questions. But let's see if we can work through a few of...

@hrasoa The App Shell model is compatible with SSR. You can use SSR for the initial visit to the page, and it will be used for subsequent visits from any...

Hello @pimterry! `workbox-precaching` allows you to precache opaque responses by default, i.e. there is no requirement that cross-origin URLs in your precache list are served with CORS. Using SRI with...

Over the years, I've found that there's a non-trivial number of folks who deploy all their locally-built subresources to a CDN, and then use the [`modifyURLPrefix`](https://developers.google.com/web/tools/workbox/reference-docs/latest/module-workbox-webpack-plugin.GenerateSW#parameter_1:~:text=used.-,modifyURLPrefix) option to prepend the...

Thinking out load some more: we might be able to address this inside of the `workbox-precaching` `install` handler, by detecting `cache.put()` quota errors there, and using it as a signal...

There's not a specific solution in place for Workbox v3. You'd have to trim down the amount/size of URLs that you're precaching. Coming up with an automated solution is going...

Hello @budarin—there's no one-size-fits all solution here, so we've kept this open to track possibilities. Listening for an `installing` service worker entering the `redundant` stage is a valid way of...

Clearing the cache can be done with the standard Cache Storage API methods: ```js import {cacheNames} from 'workbox-core'; // Call this as your custom quota error callback, or anywhere else:...

Additionally, refactor a lot of the logic into smaller pieces chained together via arrow functions, which would help with reading the generated code.