Skip to content
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

Update libraries to latest versions and Svelte to next.120 #189

Merged
merged 3 commits into from
May 3, 2024

Conversation

rgieseke
Copy link
Contributor

@rgieseke rgieseke commented May 2, 2024

I tried running the Layercake repo with an update to the Svelte 5 release candidate. I managed to get it to run with next.120.

However, I had to disable using the Nav component in the main +layout.svelte.

Error was
ReferenceError: Nav is not defined

I had this error as well when I had tried this with an earlier pre-release (<next.100 IIRC).

The components and examples seem to run fine at first looking around. That's great as it would mean that the library (given Svelte 5's promise for compatibility with the old APIs) should (mostly?) just work.

So I guess it's about getting the website itself to run.

When I update to next.120 the Layercake website disappears after an initial load.

The console error message is

Uncaught (in promise) TypeError: (intermediate value)(...) is undefined
    Svg Svg.svelte:35

Needed to disable using the Nav component.
Error was
`ReferenceError: Nav is not defined`
@mhkeller
Copy link
Owner

mhkeller commented May 2, 2024

Thanks for putting his together. Would be good to keep the Nav in. Does it help if you remove the ts declaration? Weird it’s saying it’s just not defined.

@rgieseke rgieseke marked this pull request as draft May 2, 2024 20:44
@rgieseke
Copy link
Contributor Author

rgieseke commented May 2, 2024

Sure, and good idea! Removing lang="ts" allows the Nav to work.

@rgieseke
Copy link
Contributor Author

rgieseke commented May 2, 2024

next.121 still errors.

This is likely the issue to track for this: sveltejs/svelte#11429

@mhkeller
Copy link
Owner

mhkeller commented May 2, 2024

How does it look using just 120?

@rgieseke
Copy link
Contributor Author

rgieseke commented May 3, 2024

120 looked ok and now 123 has fixed the other problem!

I haven't checked every page, but examples, components work. Looking good!

@rgieseke rgieseke marked this pull request as ready for review May 3, 2024 14:28
@mhkeller
Copy link
Owner

mhkeller commented May 3, 2024

Very cool thanks! I'll merge this into the svelte-5 branch and then figure out a plan for merging that branch

@mhkeller mhkeller merged commit 9d8bf82 into mhkeller:svelte-5 May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants