Virtual-DOM and DOM-Delegator implicit peer dependency

[kumavis]

Discovered this when using a later version of virtual-dom that uses ev-store instead of data-set. dom-delegator expects data-set. Ideally this would be decoupled instead of just moving to ev-store.

22:17 <kumavis> Raynos: playing with mercury, getting some weird behaviour
22:18 <kumavis> somehow event registration is not working?
22:55 <kumavis> Raynos: I think it was latest that im manually brininging in modules instead of using mercury and the latest virtual-dom is not compatible somehow
22:57 <kumavis> Raynos: just confirmed this to be true
23:22 <kumavis> ah ok that took awhile, but there is an implicit expectation that virtual-dom and DOMDelegator are both using data-set
23:23 <kumavis> later virtual-dom uses ev-store instead

[kumavis]

I'm not sure what other requirements there are to upgrade

[Raynos]

@kumavis just published mercury@13 to fix this.

I dont really know how to fix this peer dependency.

[neonstalwart]

I believe the open issue is that there is an implicit peer dependency where dom-delegator and virtual-dom need to be sharing a reference to the same ev-store. if they each got their own copy then it won't work.

[kumavis]

seems like vdom should supply its ev-store obj and dom-delegator should take it in

right now its just magic that they end up with the same thing

[neonstalwart]

@kumavis 👍