Joaquín Sánchez

If working we should apply the same for fonts and fonts.css entries: ```ts navigateFallbackDenylist: [/\.(ttf|woff2|otf)$/, /^\/fonts\.css$/, /^\/assets\/locales\//], runtimeCaching: [{ // urlPattern: ({ sameOrigin, url }) => sameOrigin && /\.(ttf|woff2|otf)$/.test(url.pathname), urlPattern:...

@ad1992 we've the same `cacheName` for fonts and fonts.css file with distinct expiration options, we should store them in separated caches or include both in the regex

@ad1992 `globIgnores` is for build time, `navigateFallbackDenylist` is for runtime: `globIgnores` will prevent adding local assets to the sw precache manifest (`self.__WB_MANIFEST`), while `navigateFallbackDenylist` will prevent the sw to intercept...

@ad1992 try adding the `navigateFallbackDenylist`

@xmlking what build are you using? All pages generated without any script, and cannot register sw (build + preview)...

@bytesagar if you want to use your custom sw you need to add `strategies: 'injectManifest'` to pwa options, otherwise it will not be compiled by the plugin and you cannot...

@bytesagar yes, but must remove filename and srcDir options (check src/types.ts module). Beware, default registerType option is prompt for update and so you need to use a virtual pwa module,...

@bytesagar check your cache headers: https://vite-pwa-org.netlify.app/deployment/#cache-control

@emmanuelgeoffray You must deal with this, you have 2 solutions: - change your build pipeline to keep also on server old assets and remove clear old cached assets from the...

@emmanuelgeoffray you should check the cache headers you're using, just allow browser use it: https://vite-pwa-org.netlify.app/deployment/#cache-control