Svelte 5 (5.0.0-next.167): Upgrading to the latest Svelte 5 breaks SvelteKit routing

[Serator]

Describe the bug

Page content is not rendered when going to the next page

iShot_2024-06-30_02.56.25.mp4

Reproduction

• Svelte 5.0.0-next.167 🔴
• Svelte 5.0.0-next.166 🟢

Logs

No response

System Info

Binaries:
    Node: 20.10.0 - /usr/local/bin/node
    npm: 10.2.3 - /usr/local/bin/npm
  Browsers:
    Chrome: 126.0.6478.127
    Chrome Canary: 128.0.6566.0
    Firefox Nightly: 124.0a1
    Safari: 17.5
  npmPackages:
    svelte: 5.0.0-next.167 => 5.0.0-next.167

Severity

blocking an upgrade

[lumosminima]

SvelteKit SPA are broken too, navigations aren't resetting the layout and previous page's DOM and {#await} calls get overlapped. Reloading works as shown above. Thought I missed a breaking change in changelong but it doesn't say anything about this.

[zachczx]

Same for me, upgrading to 167 broke routing for dev server. A hard refresh solves it. Preview mode doesn't carry this issue.

[JonathanPicques]

Having the same issue, navigating back and forth using the history remounts the page under the one that should have been unmounted

[Hyp3rbole]

Having the same issue. Breaks navigation, requires a refresh to render page.

[jeremieguy1]

Facing the same issue since the 167 (ok in 166), thanks for the report !

[pheuter]

Still seeing similar rendering issues during client-side routing with next.168, where the first client-side navigate to a new route appears to succeed, but all subsequent ones do not render.

[mylastore]

I went back to next.166 and it started working again.

[frederikhors]

@dummdidumm Please re-open this: is broken with 167, 168 and 169. 166 OK.

[pheuter]

next.169 works if you temporarily disable hmr in your svelte.config.js:

compilerOptions: {
    hmr: false
}