update browser when WasmServer recompiles the code on the backend about masc HOT 2 OPEN

Any thoughts on how we should maintain state across reloads?

from masc.

Any thoughts on how we should maintain state across reloads?

It really depends on the objectives of the project and where you want the state to live.

One way is to use NATS Jetstream which is reactive, so many clients get updated on a single state change.

Server: https://github.com/nats-io/nats-server
Client: https://github.com/nats-io/nats.go compiles to WASM.

Then from there it is possible to trigger updates at the many levels of granularity that are needed. Even the Props via the NATS KV store.

1. On WASM binary change, sent event to Client, and it does full reload.
2. On user data state change, NATS can automatically trigger state updates to the Client and so the client can re-render the "views" linked to that golang struct state.

You can also just use a SSE Proxy and so then there is no need to import NATS.go to the client wasm.

from masc.