LOADING_ON_ACCESSOR
<Loading on> received a function (an accessor) instead of the dependency's value; it is never called, so the boundary never re-arms.
What you saw
- Kind:
async - Severity:
warn(code that works but is structurally wrong or expensive)
The console report opens with [LOADING_ON_ACCESSOR] 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: "LOADING_ON_ACCESSOR", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
A Loading boundary's on received a function, such as on={route} or on={() => route()}.
How to fix it
on takes the dependency's value, so pass on={route()}, or on={[query(), page()]} for several dependencies.
An accessor passed instead is never called, nothing is read, and the boundary never re-arms.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while LOADING_ON_ACCESSOR 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.