upgrade of full stack causes failures due to mismatched frontend/backend versions

I am finding that when the deployed version has been updated, the server function endpoints change and the client starts generating errors (it is still trying to access the old end points which are somehow hashed). 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:

```

```

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.

Unfortunately, I don't think I can use Dioxus full stack for anything serious while this problem remains.

_Originally posted by @brianmay in https://github.com/DioxusLabs/dioxus/discussions/3496_