Svelte 5 migration

[vlrevolution]

I guess we should start discussing migration to Svelte 5 here. Anybody working on it yet?

[Muhammed-Rahif]

Can the svelte 5 migration script handle this? https://svelte.dev/docs/svelte/v5-migration-guide#Migration-script

[vlrevolution]

We should also keep backward compatibility with Svelte 4 because not everybody will transition right away due to some core libraries not yet migrated

[CodeDoes]

We just need to change the mount, for new projects (which automatically use svelte5).

import {mount} from "svelte"
const app = mount(App,{
  target: document.getElementById('app'),
});

[raiyanihiren]

@CodeDoes Right, but it's still not refreshing the DOM in Svelte when the variable changes. This was working in Svelte 4.

[michielwittkampf]

Progress on a version for Svelte 5 will be much appreciated 👍

[peterkrueck]

I'm currently considering using F7 for a Svelte 5 project. Can F7 handle Svelte 5 in legacy mode (no runes, but stores)? Or is F7 fundamentally incompatible with Svelte 5 and one needs to downgrade to Svelte 4?

[fmp777]

I'm currently considering using F7 for a Svelte 5 project. Can F7 handle Svelte 5 in legacy mode (no runes, but stores)? Or is F7 fundamentally incompatible with Svelte 5 and one needs to downgrade to Svelte 4?

In my tests, a lot does work in legacy mode, but there's some really funky breakage when it comes to "href" based routing / more complex routing scenarios. If your app is super simple spa, it'll probably work fine. I'm still debugging it, but crazy things like a total breakage of reactivity or even the ability to SET a store's value breaks down.

[fmp777]

https://svelte.dev/docs/svelte/v5-migration-guide#Migration-script

no, due to how its built, svelte's migration script just errors on every component:

@migration-task Error while migrating Svelte code: $$props is used together with named props in a way that cannot be automatically migrated.