sw-extension-audio VS workbox

I think you want to dynamically update what is currently streaming/what will be streamed next and set that data at navigator.mediaSession.metadata, e.g., see the branches at https://github.com/guest271314/sw-extension-audio.

See https://github.com/guest271314/sw-extension-audio

We use the Workbox library and its utilities as a foundation for our service worker.

Btw, Workbox is effectively deprecated now. The dev in charge of it left Google for a real company 6+ months ago and no one has filled his shoes. The other day, the lady who is "maintaining" it now finally acknowledged that nothing is going to happen to it any time soon. https://github.com/GoogleChrome/workbox/issues/3149

Start from the https://github.com/GoogleChrome/workbox

Look into Workbox if you're okay writing code for that or Progressier otherwise.

If you want to try some of these patterns, you can use the https://developers.google.com/web/tools/workbox library that provides all the features out-of-the-box.

Here is an example using workbox.

I recently had a tiny website project which I wanted to make available offline. This is achieved by adding a Service Worker. And thanks to projects like workbox, getting basic functionality like caching for offline-use is fairly easy to set up.