Open akkie opened 1 month ago
Thanks! I didn't read the Svelte 5 changelog. For Svelte 5 support, it would be a new major version, perhaps I can release it under the @next
version for now. For future releases, icon updates should be considered minor.
Is that good? looking for advice.
Yes, a @next tagged version would be awesome.
Any news here?
I was not prepared for all icons to be forced 1em 😂
Hi,
I have seen that you have added support for Svelte 5 with #25. But this isn't enough, because the lib uses SvelteComponent under the hood for the declaration of an icon. But this type is deprecated in favour of the new Component type: https://svelte-5-preview.vercel.app/docs/breaking-changes#components-are-no-longer-classes-component-typing-changes
So it's currently not possible to pass icon components around, without a TypeScript error, when using Svelte 5 because of the incompatible type. Sure it renders, but TypeScript shows an error.