Deprecation of Vue and Solid integrations

[mattgperry]

Hi everyone!

A bit of bad news to start the year 😅

I'm deprecating the Vue and Solid integrations of Motion One. The reason being, they have low usage next to the core package. Between work and parenthood I have quite little time for side-projects so I haven't been able to support these to the standard I'd prefer.

With Motion One it's quite easy to justify the little time I do spend on it as improvements to it often end up in Framer Motion (and vice versa!) However with the view library integrations I can't say the same.

I've been meaning to do this for quite a while but currently some dependency issue is blocking autoplay so I decided to pull the trigger today.

A PR to remove these packages will be merged next week.

In the meantime I would encourage anyone who has an interest in keeping these packages to fork the code and release their own library. I'll gladly link to your docs from motion.dev/vue and motion.dev/solid when you have them ready!

[productdevbook]

oku-ui/motion

I'll provide Vue and Nuxt support from here, don't worry. ❤️

[productdevbook]

@mattgperry oku-ui.com/motion

[mattgperry]

Great, thanks for taking this on!

[thetarnav]

Happy new year 😄
I think that's a good decision, I'm sure it will benefit the development of both motionone and framework integrations.
In the meantime we've moved the existing Solid integration to solidjs-community/solid-motionone.

[mattgperry]

Amazing news @thetarnav !

[thetarnav]

@mattgperry could you deprecate the @motionone/solid package on npm, with a link to this discussion?

[mattgperry]

Sure well I've deprecated it with a link to your repo instead