STRICT_READ_UNTRACKED
Untracked reactive read in component/effect body.
What you saw
- Kind:
strict-read - Severity:
warn(code that works but is structurally wrong or expensive)
The console report opens with [STRICT_READ_UNTRACKED] and the message, then an in line naming the owners that enclose the subject, root first, and an at line with the source location when the code was compiled with one.
In a captured artifact the same finding is an event with code: "STRICT_READ_UNTRACKED", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
A reactive value was read outside any tracking scope (e.g. destructured props or a signal called in the component body). The read got the current value once and will never update.
How to fix it
Move the read into a tracking scope: JSX, a memo, or an effect's compute function.
If you intentionally want a one-time snapshot, wrap the read in untrack() to say so explicitly.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while STRICT_READ_UNTRACKED is among them, with the events as evidence; after the fix, the code is gone from artifact.diagnostics.
Check for regressions in tests shows the loop and the Vitest matcher form.
Learn more
- Diagnostics: every code, with its kind, severity, and trigger.
- Debugging reactivity: how to read a report and what each group of codes points at.