-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Precache issue after new build #451
Comments
For some reason removing precaching worked now. It would be nice if there was an easy way to just disable all precaching. |
As a temporary workaround I have reverted to using version 3.2.0. |
Related to network first support also listed in #406 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: