-
Notifications
You must be signed in to change notification settings - Fork 47
Svelte 5 support #166
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
Comments
For sure - once it's stable we'll upgrade to Svelte 5 and bump a major version |
Svelte 5 is now stable. |
This package is dead. Pull requests from years ago not taken care of... |
Not dead, but also not a ton of maintainers. I do merge pr's when they come up. I don't see any in the list of open ones that seem important, but if you think otherwise drop a link to which one and I'll take a look |
Sorry if my previous comment sounded rude. That was not my intention. I just think either merge or close the PRs. It's not a good sign for potential future contributors if pull requests are laying around for more than a year. |
So, does this package support svelte 5 (runes)? |
Not yet. Should still be compatible with Svelte 5 though. Svelte 5 in general should still work with Svelte 4 code. But yeah - Svelte 5 support is coming |
Any plans to more fully support Svelte 5 now that's in release candidate?
The most notable change to bring
svelte-file-dropzone
in line with deprecations etc would just be to replace events (on:drag
etc) with callbacks (ondrag
etc).I've also noticed that many
svelte-file-dropzone
props aren't properly reactive when I use it in a Svelte 5 (runes mode) environment. I haven't dug too far into it yet, but my first guess from a quick skim of the codebase is how events are composed.The text was updated successfully, but these errors were encountered: