updating wasm for full stack

[brianmay]

I am finding that when the deployed version has been updated, the server function endpoints change and the client starts generating errors (I think because it is still trying to access the old end points). This requires force reloading the client (e.g. shift click the reload button in Firefox IIRC). IIRC just clicking reload doesn't work.

Because everything is in the client, we are not downloading html pages with the correct references. And in any case it looks like the wasm is linked to directly without any hashing in the filename:

<link rel="preload" href="/./wasm/penguin_nurse_bg.wasm" as="fetch" type="application/wasm" crossorigin="">
<link rel="preload" href="/./wasm/penguin_nurse.js" as="script">

Which is OK for me, not OK if I want to deploy websites that others will use.

Is there any better way of handling this?

I don't think there is anything I missed in the docs on this, but I might have missed something.