The server should warn if the versions do not match. Note, however, in cases LiveView is pre-bundled, such as in the LiveDashboard, this can cause conflicts. We may need a way to opt-out of the warning. Another option is to have the server send the version and the client warn, but the warning may be hidden.
Would the implementer control the versioning, since some changes may require a reloaded client and others may not? (Edit: I'm probably misunderstanding what kind of versioning this is about :D)
I'm thinking the versioning refers to the same version of LiveView on the JS side and the Phoenix side? I've been in the position where I do update via mix.deps but forget to also update the node modules. Is this the versioning mismatch that this issue is about?
Yes!
Most helpful comment
I'm thinking the versioning refers to the same version of LiveView on the JS side and the Phoenix side? I've been in the position where I do update via
mix.depsbut forget to also update the node modules. Is this the versioning mismatch that this issue is about?