I got the warnning `state_referenced_locally` when using `superForm`

[jijiseong]

• Before posting an issue, read the FAQ and search the previous issues.

Description
A clear and concise description of what the bug is, and, unless obvious, what you expected instead.

<script lang="ts">

  import type { PageData } from "./$types";

  type Props = {
      data: PageData;
    };
  
  let { data }: Props = $props();

  const form = superForm(data.form, {
    validators: zod4Client(recommendSchema)
  });
</script>

how resolve this warnning? Is it superForm internal error?

If applicable, a MRE
Use this template project to create a minimal reproducible example that you can link to here: https://sveltelab.dev/github.com/ciscoheat/superforms-examples/tree/zod (right click to open in a new tab)

[kmalloy24]

I believe this was introduced in Svelte 5.45.3 through sveltejs/svelte#17266, which extended the state_referenced_locally warning to include props (previously it only applied to $state/$derived).

The warning now fires when reading props synchronously, which catches real reactivity bugs, but also creates false positives for legitimate patterns like form initialization where we want to get the initial value - which the team acknowledged in the PR.

My understanding is that superForm(data.form, ...) intentionally captures the initial value at component creation. The form manages its own internal state and doesn't need to be reactive to subsequent data.form changes. Making it reactive would incorrectly re-initialize the form.

Until/if the warning is made less broad I've been using // svelte-ignore state_referenced_locally to suppress it. You could also downgrade to 5.45.2

[jijiseong]

I believe this was introduced in Svelte 5.45.3 through sveltejs/svelte#17266, which extended the state_referenced_locally warning to include props (previously it only applied to $state/$derived).

The warning now fires when reading props synchronously, which catches real reactivity bugs, but also creates false positives for legitimate patterns like form initialization where we want to get the initial value - which the team acknowledged in the PR.

My understanding is that superForm(data.form, ...) intentionally captures the initial value at component creation. The form manages its own internal state and doesn't need to be reactive to subsequent data.form changes. Making it reactive would incorrectly re-initialize the form.

Until/if the warning is made less broad I've been using // svelte-ignore state_referenced_locally to suppress it. You could also downgrade to 5.45.2

Thankyou for your reply
Using untrack is also a solution

  import { untrack } from "svelte";

  const form = superForm(
    untrack(() => data.form),
    {
      validators: zod4Client(recommendSchema)
    }
  );