Aah.. ok.
Yeah. The transition could be a bit thorny. In principle, we could build the reverse equivalent of html2hyperscript, but in practice, most hyperscript is likely to be so intertwined with the widget’s js, that it could quickly become a nightmare.
I suppose the simplest solution is to retain hyperscript support for a while, and perhaps deprecate it down the line?