Yes, but not automatically yet! We are actively working on our WPT infrastructure (which relies on a full Web Driver implementation) and running it manually at the moment. Once we've got it stable and automated, we'll look at pushing results to the common dashboard at https://wpt.fyi/ :)
I'm popping in here to say, I've had people from both Vue and React join my team where we're using lit-html. Transitions have been seamless, mental models map over quite well.
There's so much less cruft and overhead with lit-html, and you get speed that's akin to vanilla JavaScript. As for JSX, I think we can all get used to something non-standard, which after enough time feels normal, but the benefits of a lit-html are so immediately apparent. The transition is super easy.
Is this doing a full re-render on each change? Having not seen the state management piece... but could be nice for progressive enhancement modules in a server-rendered app. I've done similar in JS.
Nope! It doesn't visit each node like vdom. VDOM visits every virtual node. lit-html looks at only the expressions. That's where a lot of the speed/performance comes from
zeptime's correct. lit-html places markers in the HTML where the expressions are. Then it renders the HTML once, and updates the expressions directly. That's how it avoids a full re-render and avoids building am in-memory VDOM and doing any diffing.
I built a little Polymer wrapper for stripe elements </plug> unfortunately, it only works with the polyfill. It seems at first blush to be an issue between Stripe's react components and shadowDOM.