Hot Module Replacement

[cchirag]

The current approach for viewing changes in the application is to restart it. In a big enough application, restarting the app loses any state created during the application's lifecycle. This is causing a drop in development velocity. The idea is to provide a way to enable hot module replacement via options, which can be enabled or disabled with a flag. The app rerenders every time a dependency changes, while maintaining the state of the application.

[lrstanley]

I think this is less of a bubbletea issue, and more of a Go issue. There are things you could do as far as Go plugins, but plugins are incomplete and don't work consistently across systems (and alternatives like what hashicorp does for their plugin system I can't imagine would be easy to adapt to a TUI app, not to mention performance concerns). You could have state serializable, but most folks store things in their applications/components/etc that are not serializable, so I don't foresee a trivial path forward.

I would recommend selectively persisting your own state for the application, so upon restarting, it can reload from a JSON file, sqlite database, etc.