The Cache interface provides a storage mechanism for Request
Response object pairs that are cached, for example as part of
`web.workers.ServiceWorker` life cycle. Note that the Cache interface
exposed to windowed scopes as well as workers. You don't have
use it in conjunction with service workers, even though it is
in the service worker spec.

The CacheStorage interface represents the storage for `web.service-workers.Cache`

The Client interface represents an executable context such as
`web.workers.Worker`, or a `web.workers.SharedWorker`. `web.Window`
are represented by the more-specific `web.service-workers.WindowClient`.
can get Client/WindowClient objects from methods such as `Clients.matchAll()`
`Clients.get()`.

web.service-workers interfaces.

The ExtendableMessageEvent interface of the `ServiceWorker API`
the event object of a message event fired on a service worker
a channel message is received on the `web.workers.ServiceWorkerGlobalScope`
another context) — extends the lifetime of such events.

The NavigationPreloadManager interface of the the Service Worker
provides methods for managing the preloading of resources with
service worker.

The parameter passed into the `onnotificationclick` handler,
NotificationEvent interface represents a notification click event
is dispatched on the `web.workers.ServiceWorkerGlobalScope` of
`web.workers.ServiceWorker`.

The PushManager interface of the Push API provides a way to receive
from third-party servers as well as request URLs for push notifications.

The PushMessageData interface of the Push API provides methods
let you retrieve the push data sent by a server in various formats.

The PushSubscription interface of the Push API provides a subcription's
endpoint and allows unsubscription from a push service.

The SyncManager interface of the the ServiceWorker API provides
interface for registering and listing sync registrations.

The WindowClient interface of the ServiceWorker API represents
scope of a service worker client that is a document in a browser
controlled by an active worker. The service worker client independently
and uses a service worker for its own loading and sub-resources.