What are the ways we can reduce caching of wasm bi...
# compose-web
m
What are the ways we can reduce caching of wasm binary? I have this challenge in that my client has to reload/refresh page to update the app. If they just reopen they still get the old app
e
I added a suffix to the URL in the index.html: "?v=${hash of the wasm file}". In this way ensure that old caches are invalidated
m
So like this?
Copy code
<script type="application/javascript" src="composeApp.js?v=${hash of the wasm file}"></script>
The project generates two .wasm files on build. Which one do you choose?
a
Hosting with Conditional Headers maybe?
e
I forgot it has changed. My app still uses a previous version that generates wasm files with well-known names. I tried too adding a version tag in the context path. It invalidated all the static files of the old version but I had problems developing with webpack and didn't go on
m
@Arjan van Wieringen “no store” on composeApp.js and *.wasm files?
a
Etag