Svelte 5 support

[geoextra]

When using the Calendar component in a Svelte 5 project it relies on get_current_component() from svelte/internal which has been removed.

calendar/packages/core/src/Calendar.svelte

Line 4 in d337436

import {destroy_component, get_current_component} from 'svelte/internal';

A possible solution is presented here with an example.

Tested with Svelte 5.0.0-next.50.

[vkurko]

Thanks for the tip. Svelte 5 support will definitely come in the future.

[bayaderpack]

This is not only place with svelte/internal there is like 100 more places unfortunately

[dummdidumm]

Svelte maintainer here. I'm interested in why you had to reach into svelte/internal. When you start the migration towards Svelte 5, I'm curious to hear if there's anything that Svelte 5 lacks that you need to not reach into internals again.

[vkurko]

Svelte maintainer here. I'm interested in why you had to reach into svelte/internal. When you start the migration towards Svelte 5, I'm curious to hear if there's anything that Svelte 5 lacks that you need to not reach into internals again.

Author of Event Calendar here 😃. @dummdidumm Thanks for the intervention. I would like to inform you that at the moment the migration to Svelte 5 has not yet been carried out.

The reason for using svelte/internal is that there are really useful functions there that will already be present in the final code, so it makes sense to reuse them in my library rather than write my own code. And for example get_current_component() it is impossible to write my own analogue.