New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prep for Svelte 5 #54
Comments
Interesting! I've only just started tentatively using Svelte 5 for some new projects. I do believe that Svelte 4 is meant to work in Svelte 5, so it might be worth investigating this problem and filing an issue with Svelte with the findings. |
Ah, I think we're getting closer. The issue is not the store, but the fact that |
As a first step, I've allowed Svelte 5 as a peer dependency: f0d832f I really thought that |
sveltejs/svelte#11348 landed yesterday. I think it's definitely relevant, as I was seeing that error from |
I just did this and it worked fine. Integration tests passed. diff --git a/package.json b/package.json
index 9d6d9c5..29984a2 100644
--- a/package.json
+++ b/package.json
@@ -186,7 +186,7 @@
"prettier-plugin-svelte": "^2.8.0",
"prettier-plugin-tailwindcss": "^0.5.6",
"publint": "^0.2.4",
- "svelte": "^4.0.0",
+ "svelte": "5.0.0-next.120",
"svelte-check": "^3.5.2",
"tailwindcss": "^3.3.5",
"tslib": "^2.6.2", |
That's great news! Hopefully it was the |
Thanks to Mark, and everyone helping make Clerk work well with Sveltekit.
I was hoping to create a tracking issue and figure out what needs to happen to make
clerk-sveltekit
work with Svelte 5. When I tried Svelte 5 in my own project, components that wrapClerkLoaded
were no longer present. The code forClerkLoaded
is just:so it seems like the
if
is evaluating tofalse
and theslot
is not shown.Since Svelte 5 is introducing the
$state
rune, presumably we would need to hold theClerk
instance in$state
, rather than aWritable
store. Based on the docs, I expected Svelte 5 not to break Svelte 4 code, but stores might be an exception.Anyone have ideas?
The text was updated successfully, but these errors were encountered: