Svelte 5 support #19
Open
Svelte 5 support #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Updating the use of reactive variables to runes for svelte 5 compatibility
|
@basaran can you review and pull :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issues
As noted in issue #17, the library currently is not compatible with the svelte 5 runes mode. The use of reactive variables with the$: and $ $restProps is deprecated since the introduction of runes.
Description
I have updated the 3 components Splide.svelte, SplideSlide.svelte & SplideTrack.svelte and refactored them with the use of runes for svelte 5 support.