Skip to main content

ExpirationPlugin

First added

Workbox

About

This plugin can be used in a Strategy to regularly enforce a limit on the age and/or the number of cached requests.

It can only be used with Strategy instances that have a custom cacheName property set. In other words, it can't be used to expire entries in strategies that use the default runtime cache name.

Whenever a cached response is used or updated, this plugin will look at the associated cache and remove any old or extra responses.

When using maxAgeSeconds, responses may be used once after being expired because the expiration clean up does not occur until after the cached response has been used. If the response has a "Date" header, then a lightweight expiration check is performed, and the response will not be used immediately.

When using maxEntries, the least recently requested entry will be removed from the cache.

Options

  • maxEntries — The maximum number of entries to cache. Entries used (if maxAgeFrom is "last-used") or fetched from the network (if maxAgeFrom is "last-fetched") least recently will be removed as the maximum is reached.
  • maxAgeSeconds — The maximum age of an entry before it's treated as stale and removed.
  • matchOptions — The CacheQueryOptions that will be used when calling delete() on the cache.
  • purgeOnQuotaError — Whether to opt this cache into automatic deletion if the available storage quota has been exceeded.

Methods and fields

  • async deleteCacheAndMetadata() — Deletes the underlying Cache instance associated with this instance and the metadata from IndexedDB used to keep track of expiration details.

Usage

import { CacheFirst, ExpirationPlugin } from "serwist";
import { registerRoute } from "serwist/legacy";

registerRoute(
  ({ request }) => request.destination === "image",
  new CacheFirst({
    cacheName: "image-cache",
    plugins: [
      new ExpirationPlugin({
        maxEntries: 20,
        maxAgeSeconds: 24 * 60 * 60,
      }),
    ],
  }),
);