components still not unmounted

[Kapsonfire-DE]

Describe the bug

Same as
#12247
#12244
#12243

Reproduction

https://www.sveltelab.dev/vnsnqujbs0xif3c

please go to the sysadmin subfolder
This happens when a +layout.server.ts is present. Delete it, and it works

Logs

No response

System Info

next.169

Severity

blocking all usage of svelte

[AlbertMarashi]

Happening for me,and i'm not using a +layout.sever.ts either

[Kapsonfire-DE]

@AlbertMarashi can you try to find out when this happen to you? probably with a minimal repro

[AlbertMarashi]

@Kapsonfire-DE downgrading to 165 supposedly fixed the issue

[dummdidumm]

Setting hmr: false in your compilerOptions inside svelte.config.js also helps avoid the issue while a fix is underway

[Kapsonfire-DE]

Setting hmr: false in your compilerOptions inside svelte.config.js also helps avoid the issue while a fix is underway

I'd rather downgrade than not using hmr^^

[frederikhors]

@Kapsonfire-DE downgrading to 165 supposedly fixed the issue

166 also works.

[Rich-Harris]

This should be fixed by 5.0.0-next.171, via #12258

[Kapsonfire-DE]

@Rich-Harris can confirm, issue solved for me. gonna close this one

[jamesst20]

Thanks @Rich-Harris This fixed also an issue with Inertia not injecting headers anymore in page visit when I clicked anchor links. It only happened when Vite dev server was running. Not sure how this relate to this issue but it had started to happen with next.167