Joaquín Sánchez
Joaquín Sánchez
@emmanuelgeoffray upps,sorry man, the problem was about `maximumFileSizeToCacheInBytes`, you should check your app is working properly, on build you should see workbox-build warnings.
@andr-ec we cannot change it, it is workbox internal, I'll check if we can detect it and throw an error if some variable enable (by default will be enabled, will...
what's the nuxt command you're using to build the app? If the content is dynamic, you should exclude `/api/*` calls from the sw (`navigateFallbackDenylist`) and add a custom runtime caching...
Since you're using Netlify, add [registerWebManifestInRouteRules: true](https://github.com/vite-pwa/nuxt/blob/main/src/types.ts#L47) to pwa configuration (this will solve the problem with sw.js and webmanifest content type)
Another solution that may work is using `navigateFallback: undefined` and let nuxt error do its work: https://github.com/vite-pwa/nuxt/issues/53
I'm asking if you're using `nuxi geneerate` or `nuxi build`... do you have api folder in the output folder?
The sw is for browser clients, there is no way to use sw per client (browser tabs or instances), sw is shared across all its clients: you can get a...
Where is rhe api folder? I mean, where is the api folder generated?
Check src/config.ts in nuxt repo in the pwa org., if it is outside the public folder api will not be included
check this: https://vite-pwa-org.netlify.app/guide/periodic-sw-updates.html#handling-edge-cases