Currently, Elmish-Store maintains an internal map of all store instances to preserve state when createStore is invoked with the same key again, which is particularly useful for scenarios like Hot Module Replacement (HMR). Nonetheless, there are situations where the store's code may be reloaded, necessitating the integration of true HMR capabilities that leverage the tools provided by bundlers. As a starting point, integrating with Vite would be beneficial, given its popularity.
Furthermore, the process of rebuilding the state could be optimized to account for potential changes in the model type. For inspiration on implementing this feature, consider examining the approach taken in the Fable.Solid implementation.
Currently, Elmish-Store maintains an internal map of all store instances to preserve state when createStore is invoked with the same key again, which is particularly useful for scenarios like Hot Module Replacement (HMR). Nonetheless, there are situations where the store's code may be reloaded, necessitating the integration of true HMR capabilities that leverage the tools provided by bundlers. As a starting point, integrating with Vite would be beneficial, given its popularity.
Furthermore, the process of rebuilding the state could be optimized to account for potential changes in the model type. For inspiration on implementing this feature, consider examining the approach taken in the Fable.Solid implementation.