-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Description
Describe the bug
When a value is instantiated on a +page.svelte file and passed through multiple slots, it behaves unexpectedly.
In this example reproduction, I have a counter component that loops through an array of values by simply incrementing the index. The currentValue and the index are bound so they can be referenced externally.
The bound variables are then passed through for observation in two different ways, and the combination of slots causes ONE of the values to no longer update, but one continues to update correctly.
Reproduction
https://github.com/LukeHagar/svelte-min-repro
Logs
No response
System Info
System:
OS: Windows 10 10.0.22621
CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor
Memory: 6.41 GB / 31.93 GB
Binaries:
Node: 18.14.2 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 9.6.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.50)
Internet Explorer: 11.0.22621.1
npmPackages:
@sveltejs/adapter-auto: ^2.0.0 => 2.1.0
@sveltejs/kit: ^1.5.0 => 1.19.0
svelte: ^3.54.0 => 3.59.1
vite: ^4.3.0 => 4.3.9Severity
blocking an upgrade
Additional Information
I'm honestly quite confused regarding this issue and am frankly amazed at how simply it could be recreated.
Thank you all for all the work you do!
I'm a big fan of svelte and sveltekit
