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.

Sign up for GitHub

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

Jump to bottom

Build in Force Cache Invalidation After Redeployment #181

Closed

niclasheun opened this issue Feb 14, 2025 · 1 comment · Fixed by #185

Labels

bug

Contributor

niclasheun commented Feb 14, 2025

Add 'hack' such that at redeployment, the browser cache is invalidated.

niclasheun added the bug label

github-project-automation bot added this to PROMPT

Contributor Author

niclasheun commented Feb 16, 2025

After digging a bit into this topic:

All the 'usual' scripts, have already a "content-hash" in their file name. Hence, with each re-deploy this content hash changes and forces the browser to reload these files.
The issue is in the dynamically loaded models. These models rely on "remoteEntry.js" to have a fixed name. Hence, these do not have contenthash in them and are not invalidated after redeployment.

niclasheun linked a pull request

that will close this issue

Cache Invalidation After Redeployment #185

Merged

niclasheun closed this as completed in #185

github-project-automation bot moved this to Done in PROMPT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment