Describe the bug
When a {#if} condition and a component inside the block depend on the same shared state, and the component mutates that state during render, the {#if} condition no longer reacts to subsequent state changes.
This issue does not occur in version 5.41.2, but was introduced in 5.41.3.
Reproduction
https://svelte.dev/playground/595ee23e99db4a9489d88f5d800abaad?version=5.55.4
Logs
System Info
System:
OS: Windows 11 10.0.26200
CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12500H
Memory: 25.37 GB / 63.71 GB
Binaries:
Node: 20.19.5 - C:\Program Files\nodejs\node.EXE
npm: 11.12.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 147.0.7727.56
Edge: Chromium (141.0.3537.71)
Firefox: 149.0.2 - C:\Program Files\Mozilla Firefox\firefox.exe
npmPackages:
svelte: 5.55.4 => 5.55.4Severity
blocking an upgrade
Describe the bug
When a {#if} condition and a component inside the block depend on the same shared state, and the component mutates that state during render, the {#if} condition no longer reacts to subsequent state changes.
This issue does not occur in version 5.41.2, but was introduced in 5.41.3.
Reproduction
https://svelte.dev/playground/595ee23e99db4a9489d88f5d800abaad?version=5.55.4
Logs
System Info
System: OS: Windows 11 10.0.26200 CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12500H Memory: 25.37 GB / 63.71 GB Binaries: Node: 20.19.5 - C:\Program Files\nodejs\node.EXE npm: 11.12.1 - C:\Program Files\nodejs\npm.CMD Browsers: Chrome: 147.0.7727.56 Edge: Chromium (141.0.3537.71) Firefox: 149.0.2 - C:\Program Files\Mozilla Firefox\firefox.exe npmPackages: svelte: 5.55.4 => 5.55.4Severity
blocking an upgrade