Svelte 5 functionality issues

[c0repwn3r]

Works great in svelte 4. Tried in svelte 5 - this lib is incompatible with the new event system & some buttons don't appear correctly (copy-pasting the demo options, with all plugins installed):

[ngDuyAnh]

Yes, there is some initialize rendering problems with the component in Svelte 5. I had to downgrade to Svelte 4 to use it properly.

[vkurko]

Thanks, Svelte 5 support is in the works.

[ondrejrohon]

@vkurko need help?

[vkurko]

Overall, the experience of #235 can be useful. I don't have a specific plan of action right now (or rather, I initially wanted to rewrite everything from scratch, but it turned out to be too expensive, and I put this idea aside).

So if you can suggest rewriting some part of the code so that it works well in Svelte 5, then please, I'm open to such suggestions.

[Mathnerd314]

Well, the SMUI library is an example - first they simply added <svelte:options runes={false} /> to each file, then they are (still) migrating the files one by one, e.g. in this commit, changing those to runes={true}. There is an automigrate script npx sv migrate svelte-5, but it isn't complete, so doing it incrementally makes more sense IMO.

[James3UK]

@vkurko
The main change required is just renaming the store to something other than 'state' because it clashes with the svelte 5 state rune.
e.g setContext('state'); just needs to be setContext('calendarState'); or whatever.