Joaquín Sánchez

Try using `/mobile/`, your app must be under that context path. Your assets must also be under that context path, a sw with scope /mobile cannot control /assets/* or /*

this header is set only in your local dev server, you'll need to add also it on your local build + preview (if using express that header will be missing...

Try using `/mobile/` in the base and remove the scope in the pwa options, you need to run the preview using the context path `/mobile/` if using `npx serve dist`...

FYI: In a few weeks I want to release `v1.0.0`, all the deprecations will be removed.

There are a lot of options, the module will merge layers using `defu`, since the entry is an array the merge will not replace the value (we should add a...

Merging options is not easy, Nuxt will merge configured layers (I'll check the layer.ts module here, maybe we can simplify the logic) and the module requires merging again for custom...

Maybe we can add a new hook to dedupe options before resolving the configuration (providing merged configuration and the layers configuration, similar to https://github.com/vuetifyjs/nuxt-module/blob/main/src/utils/layers.ts#L85C11-L85C21). For example, adding before returning here:...

@lna1989 looks like we can use a merger function to override the value instead merging: this will require to change a lot of types. ```ts // In project layer VBtn...

@lna1989 since we have this: ```ts type DefaultsInstance = undefined | { [key: string]: undefined | Record; global?: Record; }; type DefaultsOptions = Partial; ``` can you try using previous...

Only minimal presets implemented: documented here https://vite-pwa-org.netlify.app/assets-generator/cli.html#presets (WIP) Check https://vite-pwa-org.netlify.app/assets-generator/cli.html#built-in-features to build custom presets