#m-mount

Mithril m.mount on a legacy-managed DOM node: teardown and route prefix conflicts during incremental migration

I am planning an incremental migration of a small single-page application to Mithril (v2.x) without downtime. The goal is to use m.route and m.mount so that selected routes render new Mithril components while the rest of the page continues to be served by the existing legacy framework. The open uncertainty is how Mithril's redraw and lifecycle behavior inter