Joaquín Sánchez

The service worker lifecycle is complex, we may have 2 service workers when new version detected. > Here is what I understand so far, and some related questions. > >...

Error when adding the pwa module? Provide a minimal reproduction, all my tests can install the pwa module: check https://vite-pwa-org.netlify.app/guide/scaffolding.html , follow the prompts selecting Vue when asking for Framework...

Check your cache headers: https://vite-pwa-org.netlify.app/deployment/ Then you can use configure [periodicSyncForUpdates](https://github.com/vite-pwa/nuxt/blob/main/src/types.ts#L33): for context https://vite-pwa-org.netlify.app/guide/periodic-sw-updates.html,

@ricardovanlaarhoven can you update your repro to use latest vite 5.4.0-beta.0 and switch sass api to modern? I guess there is some sass cache, starting dev server and navigating takes...

We've both svg (in figma not in the repo) and so we can add logic I added here: https://github.com/userquin/vuetify-nuxt-module/blob/main/README.md ```md Zero-config Nuxt Module for Vuetify ```

since preset is global (will be applied to all images), you can create a new config file with a custom preset for it, then add a new script running the...

You have 2 config files, last one with custom preset and run from command line with that custom file

If the favicon is generated with two.svg image, split your config file in 2 config files, the preset is global and cannot be shared between images. Keep the current configuration...

This package uses sharp to generate the icons, I have no idea why this weird output, I Will check it on my local.

> However, I discovered that when a favicon (favicon.ico) is generated, it remains in the input image's directory. Uhmm, you can provide the favicon names with the relative paths, if...