You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To my understanding the precache feature of workbox works as a cache first, not a network first. If not, the following is nonsense.
Every time I make a new build of my project and deploy it live, users have errors because assets could not be found.
It's difficult to pinpoint the issue but what I think is happening is the homepage (start_url) is being precached. So a request is never made to the server to know where the new /_nuxt/ assets are and at the same time the old assets caches have expired.
I've attempted removing the precaching but then the site doesn't work offline anymore. Any other ideas what to do or test?
I'm using the latest available version of nuxt and nuxt pwa module.
The text was updated successfully, but these errors were encountered:
To my understanding the precache feature of workbox works as a cache first, not a network first. If not, the following is nonsense.
Every time I make a new build of my project and deploy it live, users have errors because assets could not be found.
It's difficult to pinpoint the issue but what I think is happening is the homepage (start_url) is being precached. So a request is never made to the server to know where the new /_nuxt/ assets are and at the same time the old assets caches have expired.
I've attempted removing the precaching but then the site doesn't work offline anymore. Any other ideas what to do or test?
I'm using the latest available version of nuxt and nuxt pwa module.
The text was updated successfully, but these errors were encountered: