if you modify the swDest option to generate the serviceworker in other path, this not affect the path to generate the development service-worker.

I need to see the code to fix this, but would be nice to have this in the documentation.
this is the fix to generate serviceworker in development in the right path.

  dontAutoRegisterSw: true,
  devSwSrc: {
    from: './public/sw-dev.js'

What problem does this feature solve?

The @nuxtjs/firebase module provides service worker scripts for firebase auth sw sessions.

The problem is that (depending on where the script is included) it either:

• is ignored (because workbox responds with a caching strategy)
  or

We started this project not quite long after Next.js became public and we haven't really touched the README 😅

We've just been improving the code section and making it a lot better. I guess it's time to give the README a new structure, basically to pass the right message to new users.

Let's do this! 🚀

Feedback from Thomas Steiner

• You should probably add some feature detection to the APIs
• Checkout our Browser Test Tool
• Check https://web.dev/fugu-status/
• Check https://developer.mozilla.org/en-US/docs/Web/API

The current workbox-sw.js in the npm package contains the URL for JSDelivr CDN.

Even if the workbox directory is served locally, after fetching workbox-sw.js, other files will be still fetched from JSDelivr CDN, instead of the local directory.