await_reactivity_loss false positive even when used within untrack function 2

[minht11]

Describe the bug

Another bug related to #16381

import { untrack } from 'svelte'
	
	let name = $state('a')
	let count = $state(1)

	const wait = () => new Promise((resolve) => {
		setTimeout(resolve, 1000)
	})

		const promise = Promise.resolve(1)

	const getData = async () => {
		await promise
		await wait()

		// This causes false positive
		if (name === 'a') {
			
		}

		return count
	}

	let countAsync = $derived.by(() => {
		return untrack(() => getData())
	});

Reproduction

https://svelte.dev/playground/hello-world?version=5.36.7#H4sIAAAAAAAAE21Sy27jMAz8Fa5QwA5g5HF14xQFeuhxD7mte1BkJhEqS4ZEJxsY-vdCDzfpYg9-gEPOkENOTPMeWc3eUSkDV2NVByV2krBbsIodpULH6j8To9sQ8kKAVXPV6zAs3QUVhdiBO_xfXBhNqMmxmm2dsHKgXatbkv1gLMEEoybLxSd4OFrTQ5EKi5ATHoUEgRYaeHLECcuCF4sZEWbUdIc2AdAtCaMdwZXLgJULaHag8Qq_remlw7K06Iy6YASmqEQOaS97NCPNaAWb9XodpXzmnZmHRATNTLnMNf90cEJ648ShAe5uWuRWsiKP_WWqx1B4ld-KqxXsz9KB4KNDB0euHMJgnCR5yWXyCGXyqGkg2DNLJAtb8jOZRRqtTrbFwRLwbeVrbLOBpw6tvGC3PNzKH01ngry0jOUxy0U26zktb7u671tvz5tdurIpTXnX87-2q_MmZR1GIqPBaKGk-GymB_F8BY-DwgsUhwLq8N9q7-Nl7c3ppDDm1TCFjw-9JOYdqxjhX2I12RH9R8WIS3WVumN1tNZ_AXS1wwAUAwAA

Logs

System Info

Svelte 5.36.7

Severity

annoyance

[7nik]

The warning here is correct: untrack and deep tracking are still sync. After removing untrack, this derived doesn't re-run because it has no deps and this confirms $inspect.trace():
$derived.by(...) (App.svelte:25:30) no reactive dependencies

[minht11]

But thats the point, I don't want data to rerun because of dependencies inside getData. If I wanted to subscribe to it I would do before calling async function:

	let countAsync = $derived.by(() => {
		$inspect.trace();
		void count
		return untrack(() => getData())
	});

The pattern I am using I have query function which takes source and fetcher arguments. I only want for source to be tracked and everything that is accessed inside query should be not reactive, that works, but produces said warning.

[7nik]

This warning exists to hint to people when they read a state after the first await but this state isn't added to dependencies because it is impossible for now. So, in general, it is a true positive.

Talking about ways to mute the warning:

if (untrack(() => name) === 'a') {

works

---

// svelte-ignore await_reactivity_loss 
if (name === 'a') {

doesn't work - looks like a bug

---

// svelte-ignore await_reactivity_loss 
return getData()

doesn't work - impossible without Async Context which is not available in browsers

---

return untrack(() => getData())

same as the previous one

[minht11]

That is bit unfortunate because that means that useQuery like utilities will emit a lot of false positives

[elliott-with-the-longest-name-on-github]

@minht11 if you can provide an example of an actual false-positive we can look into fixing it, but @7nik is right -- this case is a true positive, and is actually why the rule exists in the first place.