purgequota

Library Affected: workbox-sw

There’s an ExpirationPlugin which we can assign to our routes. I couldn’t find in the docs though one thing that clearly states what I need to hear.

Does this clean up the whole cache for that specific route? if I set this to true for images in the specific cache called app-images and let’s say quota is exceeded, will this clean up the whole app-images cache or some part of it to shrink the size to take it down under the storage limit again?

[jeffposnick]

The goal is to avoid getting the browser close to reaching the limit again for an extended period of time, so deleting as much as the developer has opted-into is the safest default approach.

If you’d prefer to use your own customized approach to recovering from quota errors, instead of setting purgeOnQuotaError: true in the ExpirationPlugin, you can register your own custom callback with workbox-core’s registerQuotaErrorCallback() function.

[novaknole]

yeah. I get that. It might be better to only try to delete the one which caused it. maybe it’s enough to delete only one cache just to come down the limit ? why both ? That’s what i am curious.