LOADING_ON_OUTSIDE_HOLD
<Loading on> changed but its data is also read outside the boundary and holds the frame: the fallback can never be seen.
What you saw
- Kind:
async - Severity:
warn(code that works but is structurally wrong or expensive)
The console report opens with [LOADING_ON_OUTSIDE_HOLD] 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_OUTSIDE_HOLD", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
on re-armed a Loading boundary, but a source it is waiting on is also read outside the boundary and holds the frame.
The frame waits for that same source, so the fallback cannot appear.
How to fix it
Move the outside read under the boundary.
If the fallback should appear immediately beside the held frame, use a latest() read in on.
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_OUTSIDE_HOLD 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.