False positive non-state warning for bind:this

[mquandalle]

Describe the bug

If bind:this={ref} is used on an element inside a {#if reactiveState} block, the corresponding let ref declaration gets marked as "non-reactive-update" warning, which I believe is a false positive because the bind reference is still set and updated, and proxying it in $state doesn't change anything—except to remove the linter warning.

Previous issue on a similar topic #10435

Reproduction

https://svelte.dev/playground/ccd2e6f87d7e4985b5834547d4486aae?version=5.25.3

<script>
	let showDiv = $state();
	let divRef; // Warning: https://svelte.dev/e/non_reactive_update
</script>

{#if showDiv}
	<div bind:this={divRef}>Hello</div>
{/if}

System Info

Playground, svelte 5.25.3

Severity

annoyance

[MotionlessTrain]

divRef can change, though, whenever showDiv updates.
Now, reactive code which depends on divRef wouldn’t receive updates, which is what the warning is indicating
example (The text should be shown in red as well when the div is shown)

[paoloricciuti]

Correct...the reference will still get updated, which means if you are only using that variable in events for example is fine...but if you are using it in an effect that needs to rerun when it changed from undefined to defined than the warning is correct...which means the warning is correct since we don't know where you are using it.

Thanks for reporting but closing this!

[kevlarr]

Correct...the reference will still get updated, which means if you are only using that variable in events for example is fine

In that exact situation (only using the ref in events), is there a way to silence the warning without unnecessarily making the ref reactive with $state?

[paoloricciuti]

<script>
	// svelte-ignore non_reactive_update
	let div_ref;
</script>

[kevlarr]

No idea how I missed that in googling (still pretty new to svelte) 🙄 Apologies, but thanks!