Svelte version @5.0.0-next.140 breaks Svelte-dnd-action about svelte HOT 9 CLOSED

Hi, I'm the maintainer of svelte-dnd-action. Based on

Confirmed this is due to delaying rerenders. The action updates its state in an update callback which is coming in too late for the other events, meaning that 5 items instead of 4 are inside the array, and that somehow messes with the each block.

This sounds like an issue with svelte that can affect other existing actions.

from svelte.

Mmm I think is rerunning the snapshot over and over since is in the template effect.

However if it's not necessary better since it's one distraction less. I'll try to take a look later

from svelte.

Confirmed this is due to delaying rerenders. The action updates its state in an update callback which is coming in too late for the other events, meaning that 5 items instead of 4 are inside the array, and that somehow messes with the each block.

from svelte.

$state.snapshot removes reactivity so you can't expect to use snapshot and still have reactivity

from svelte.

$state.snapshot removes reactivity so you can't expect to use snapshot and still have reactivity

@paoloricciuti Is it? I'm pretty sure that the HTML/Svelte code still "reference" the reactive state variable, because it still works when I downgrade to Svelte version @5.0.0-next.139 (repl: https://www.sveltelab.dev/ql0iefy6cbg81tq - the same as the repl above, only change is downgrade svelte to @5.0.0-next.139)

from svelte.

Okay so it turns out the $state.snapshot wasn't necessary, it was me trying to fix the error, I have updated the description and repl

from svelte.

Uh 140 Is the yield effects one. I have the feeling this is either something to fix in DnD itself or something really non obvious.

from svelte.

So is this a bug that Svelte need to fix or something that svelte-dnd-actions needs to fix?

from svelte.

Fixed by #11855, we reverted the event defer changes

from svelte.