-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
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
Svelte 5 #117
Comments
Hi! I've not tried Svelte 5 yet. I think it was supposed to be backward compatible(?) |
Yes and no. They do have some breaking changes that they can't get around, although I haven't seen those impact this library (yet). They also need library authors to create a separate branch for Svelte 5 changes, particularly since eventually the changes will become breaking. It'll be advantageous to move to Svelte 5 as it addresses some shortcomings for the environment, although some people find it controversial, I suppose ("Oh no! It's become ReactJS!"). Currently, I am trying to use this library with Svelte 5, and while it works, I'm constantly having to apply --force or --legacy-peer-deps to work with my project. FWIW, this site might clarify some things, now that Svelte 5 has reached release candidate phases. |
I checked out the resources you provided and then added Feel free to answer here or open new issues for anything going wrong in the new Svelte version! |
@BearToCode hi! Long time no see 🤗 |
I also want to add that by using the new CLI command sv migrate, upgrading to Svelte 5 might be painless. The migration guide gives you an overview of the changes. |
Are there plans for Svelte 5 support? :)
The text was updated successfully, but these errors were encountered: