Svelte 5: problems unmounting elements from the dom inside an each block

[hawk93]

Describe the bug

This happens from next.168 and I can't reproduce it without kit. Opening StackBlitz you'll see that the element are correctly added to the DOM when we click open but they are not removed when we click close

Reproduction

StackBlitz

Logs

No response

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (6) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    svelte: ^5.0.0-next.168 => 5.0.0-next.168

Severity

blocking an upgrade

[Karakatiza666]

Having a similar issue, but just with an {#if} block that shows one component or the other based on a boolean value of media query - components get appended in the dom when value changes instead of replacing one another

[Serator]

Having a similar issue and it seems to be related to this one and is only reproducible in dev (HMR).

[Dudek-AMS]

same as #12247

not loop/if related

Similar issue with 168.
However, with 167, when my component is dynamically switching, while the old component is gone, the new component never appears:

<svelte:component
	this={tableOfContent.currentComponent.component}
/>

[dummdidumm]

For everyone experiencing this: you can disable hot module reloading through the compilerOptions.hmr setting until this is fixed.