Svelte 5: change in DOM update behavior about svelte HOT 4 CLOSED

Yup definitely a bug: my guess is that name is not detected as being updatable (if you look at the generated code is not a source is just a variable). Probably a missing "branch" when checking for variables that are updated.

from svelte.

In case anyone needs a temporary fix, and using $: isn't an option (because the reactive re-assignment breaks something). This allows the initial value to be set based on a prop, so that it won't be updated when the prop changes but any assignment to value will trigger updates (I think, I'm still experimenting to find what works with both versions):

export let prop

let initial = prop // and likely some other logic

$: value = initial

from svelte.

In case anyone needs a temporary fix, and using $: isn't an option (because the reactive re-assignment breaks something). This allows the initial value to be set based on a prop, so that it won't be updated when the prop changes but any assignment to value will trigger updates (I think, I'm still experimenting to find what works with both versions):

export let prop

let initial = prop // and likely some other logic

$: value = initial

You just need to reassign that variable in another place, a listener or even just this

<script>
	let display = 'none'

	$: display = display;

	function action(div) {
		display = 'block'
	}
</script>

<div style:display use:action>Hello</div>

from svelte.

I'll give that a try - I could well have been over-thinking things!

from svelte.