NO_OWNER_BOUNDARY
Boundary created without owner.
What you saw
- Kind:
lifecycle - Severity:
warn(code that works but is structurally wrong or expensive)
The console report opens with [NO_OWNER_BOUNDARY] 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: "NO_OWNER_BOUNDARY", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
A boundary was created outside any reactive context. Like an unowned effect, it needs an owner to dispose it.
How to fix it
Create it under a component or createRoot, or attach it to an existing owner with runWithOwner.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while NO_OWNER_BOUNDARY 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.