OvermindDL1

> Nice! Is there an example of bucklescript-tea using webcomponent or React hacked in? Not as of yet for React as I don't use React, but I do have it...

For proper webcomponent handling I need to implement a layer to hook the custom elements lifecycle events to loading the application instead, and make a subscription for being able to...

> There's no package-lock.json in the repo, so if you npm install on a clean clone it will grab bucklescript 4.07. That'll lead to a bunch of dirty files in...

This was an entirely planned use-case! I just never got around to it. ^.^ I was initially thinking of another pattern to do it but this hydrate way is interesting,...

For note, the original pattern I was thinking of was a new vdom function to merge a vdom into an "existing" DOM, instead of comparing two vdom's, and call the...

> Good point. I didn't think about this... Any idea how we can remove the "pre-rendered" listeners without having a reference to the actual listener (which is needed by removeEventListener)?...

> I have an issue where event handler callbacks on a div that close over information do not get replaced even when the key of the event property changes. Hmm,...

I am curious, do you use the same 'name' in other nodes in the tree? Maybe in another node that might get 'mutated' to this node or vice-versa? If so...

> Yep for sure, that's actually what I've done -- by 'patched' here I just meant amended/based on. Incidentally, is adding optional ?key parameters to the various functions in Tea_html...

> With ID you mean keyor unique? As far as I understand it, the difference wouldn't matter, as it doesn't have any children. I mean the literal id on the...