7nik

Yes, it doesn't know, but the spreading should be considered potentially reactive, like reading a prop `{foo.bar}`.

I meant an object's prop but not a component prop. My bad. Reading an object's property will always result in the dynamic output, even if it is [obviously static](https://svelte.dev/playground/hello-world?version=5.1.2#H4sIAAAAAAAAA22MOw7CMBBEr2K2SYMS0RoTiY47xBQhLCTSsrbs5SfLd8emoaGcN28mwWUhjKCHBPL2CPoLYA083mrae9_GB5JUdhoj_uOTY0GWcgMmTmHx0lu2UnAUVQdqp5qnC3RutpZN93PYzJv-gEROpSq2hHyVOa9MVwrL5VzwJaAl3DEf8wfBdbMvsAAAAA==). Spreading...

If you mean REPL with static prop - yes, though the output is the same in the rune mode.

It was fixed by #14488 (v5.3.1)

> However the UI doesn't update when state changes during an out transition: [REPL](https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAA4WPwWrEIBCGX2WY9rALC7m7SaDPUXtIom6HJio6CS3iuxfdDaHtoQcP__gN_zcJDc06onhNaIdFo8AX7_GC_OVLiJueWeMFo1vDVCZtnAJ57qWVTIt3gSGBGZSGDCa4BeRjqeEw2EhMzkq8Fry8WTNsFGmcNXTwHHlgfeKw6vN1_z72yN4OyAxzrFTbHAq2JetXhqLbSZze9fQxuk-JMJJVomatuvSozND00qYnMrtELq2tog2qIR_lohx1HzrrVg4u8hC4S6czdP0fy3JD3nGy_-H1msr3v4vJ3gSkH_lu2Sjain5DJuMFF6fIkFYoavdb_gYdJuYOzQEAAA==). I guess this might be intended, since at this point all the render effects have already...

Is updating the store the correct behaviour in the rune mode? Shouldn't it be updated only in a case like `bind:value={$store.list[i].x}`?

Btw, since #12507 ([email protected]) snippets aren't signed anymore and you can try to pass any function as a snippet (though you still can get a typing error in TS). Parameters...

Probably https://github.com/TyrealHu/acorn-typescript/issues/58

Fresh head works much better

For reference: https://github.com/sveltejs/svelte/pull/12938#issuecomment-2299767265 here is the decision to remove `$state.link`. The problem was that, after correcting the behaviour, it used the `$effect` internally anyway. Also, there were open questions about...