REACTIVE_WRITE_IN_OWNED_SCOPE
Reactive write/invalidation inside component/computation.
What you saw
- Kind:
write - Severity:
error(broken behavior)
The console report opens with [REACTIVE_WRITE_IN_OWNED_SCOPE] 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: "REACTIVE_WRITE_IN_OWNED_SCOPE", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
A signal/store write (or refresh()) executed during an owned scope — a component body or a computation.
Pure scopes must not cause state changes.
How to fix it
Move the write to an event handler or effect phase.
If the write is genuinely intentional initialization, pass the ownedWrite option on the setter call.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while REACTIVE_WRITE_IN_OWNED_SCOPE 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.