Mutation watchers in as far as checking for changes on the vdom, though my current dev iteration of bs-tea uses kind of ‘pipes’ to mark areas instead. But currently I’m not sure you mean by ‘general render function’? Do you mean calling something else to return a vdom from inside the vdom? If so then the lazy construct can do that. Do you mean rendering, say, a javascript owned element? Then not yet but that’s planned as the CustomNode, however I find webcomponents better for that anyway and should be used and work fine in the current system (as does bucklescript-tea work perfectly inside a web component, I find the whole concept of chaning javascript calls to build the DOM tree a horrible misdesign that a lot of people do for who knows what reasons, webcomponents are superior).
