Replies: 1 comment
-
I am using Skeleton 1.9 and Svelte 4 with no issues. It doesn't resolve the issue that Svelte 5 is likely to only work with SvelteKit but we can only wait and see. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For example, Skeleton has dropped support for code that isn’t running in SvelteKit and they speculate that Svelte will do the same. skeletonlabs/skeleton#721
The end of support for Svelte without SvelteKit seems to be coming soon. Our small community which includes Chrome extensions and some Electron-based apps will be on our own.
Here is a summary of the issue with Skeleton but other libraries like Carbon Components are facing similar challenges.
I don’t think this is an issue with Skeleton but is instead a dependency of Svelte 3.59 on SvelteKit which I’m not using (I’m using LiveSvelte with Phoenix). For example, if you try to use the v 1.6 Accordion component with Svelte 3.59, you will get the error described in sveltejs/svelte#6584
Uncaught (in promise) TypeError: Cannot read property '$$' of null
If there is something Skeleton-specific about this issue, it’s that Skeleton 1.6 should probably declare a dependency on ~3.58 instead of ^3.58 because this issue didn’t, for me, appear until Skeleton 1.6 was released. But perhaps the minority of non-SvelteKit users should just add that on their own, which I do.
Beta Was this translation helpful? Give feedback.
All reactions