We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Now that vanilla JS APIs are available, it would be great to have native support for Svelte 5.
An official Svelte 5 wrapper that integrates smoothly with the Runes API.
Using vanilla Motion.dev in Svelte projects, but it lacks reactivity and feels less integrated.
Svelte’s reactive model could pair well with Motion.dev, enhancing the developer experience.
The text was updated successfully, but these errors were encountered:
I just created a repo to experiment with the possibility of wrapping motion apis in svelte https://github.com/epavanello/motion-svelte
Sorry, something went wrong.
Since youre asking for Svelte support, might as well ask for
Nope @mattgperry, please let the community create wrappers themselves so you can focus on the React and Vanilla APIs <3
GLHF! This is gonna be a mess to maintain tbf.
I just completed a first minimal build with ssr and runes support. I will push the changes to the repo and the npm package soon
Here the first demo and the repo
https://motion-svelte.vercel.app/ https://github.com/epavanello/motion-svelte
No branches or pull requests
Is your feature request related to a problem? Please describe.
Now that vanilla JS APIs are available, it would be great to have native support for Svelte 5.
Describe the solution you'd like
An official Svelte 5 wrapper that integrates smoothly with the Runes API.
Describe alternatives you've considered
Using vanilla Motion.dev in Svelte projects, but it lacks reactivity and feels less integrated.
Additional context
Svelte’s reactive model could pair well with Motion.dev, enhancing the developer experience.
The text was updated successfully, but these errors were encountered: