Cache issues after deploying updated entry.worker.ts #159
Unanswered
felipetodev
asked this question in
Q&A
Replies: 2 comments 5 replies
-
When you migrate your cache, do you intend to migrate previous data there, or delete it all together and start again in a new cache? And what's the current behaviour like? @felipetodev |
Beta Was this translation helpful? Give feedback.
0 replies
-
I need a new cache when deploying with new features (a new version) and to ensure that my users see the updated app without any mismatch between the latest deployment and the previous one. @ShafSpecs e.g., error:e.g., of how it should bethis is the project btw: https://github.com/felipetodev/log.js |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello remix-pwa community!
I'm having an issue I can't figure out. Every time I deploy and update the version of my
entry.worker.ts
, my application doesn't update correctly. It's as if the previous cache persists, and only some parts of my application change or update.I'm using the following deps versions:
@remix-pwa/sw: ^3.0.10
@remix-pwa/worker-runtime: ^2.1.4
this is my entry.worker file:
I’m using an object as a dictionary to manage a configuration in my app, and when I add a new option, update the version, and deploy, this change is not reflected in my app.
I'm surely doing something wrong, but I can't identify or resolve it with the documentation. Any help would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions