Shared reactive/component core?

[agoldstein03]

Not sure if this topic has been discussed already. As best as I can tell, Vue development is currently happening mostly disconnected from the main repo. I get that React is likely the top priority, but I've seen a lot of other projects have success adopting a shared core which implements framework-agnostic behavior for handling reactivity and components. Then the React and Vue code just has to glue that core onto the framework specifics. It also makes it much easier for communities to maintain their own bindings between that core and their own framework. Generally either the core inherits from the dom package, or vice versa (depending on priorities).

I use a lot of Solid.js and would be happy to put in work to maintain such a bindings package, if there is interest in moving forward with a shared-core approach.

[mattgperry]

Hey @agoldstein03!

It's definitely true that React is the priority, simply in terms of usage this makes sense. That said I am in the slow process of moving more of the package from framer-motion to motion-dom, and that will be stuff that's guaranteed not to have any library-specific code. But it's quite a big project to disentangle so will probably take a little more time.

[agoldstein03]

Thanks so much for the quick reply! Definitely exciting to see. Is there a progress board or public-facing tracker of some kind I could subscribe to (or maybe a major version release target) regarding that transition? Just want to make sure I don't miss it as things like layout animations make their way into motion-dom 😄

And if there's room for community contributions and/or a bounty to accelerate the pace of motion support for Solid.js, I have some (albeit limited) resources I could potentially throw in that direction, just lmk