SSR_UNDECLARED_LIVE_SOURCE
A document render is still pumping an async iterable in server-component scope 5s in — declare the function live(...) or bound the source (dev).
What you saw
- Kind:
ssr - Severity:
warn(code that works but is structurally wrong or expensive)
The console report opens with [SSR_UNDECLARED_LIVE_SOURCE] 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: "SSR_UNDECLARED_LIVE_SOURCE", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
A server component rendered into a document read an async iterable that was still producing data.afterMs (5s) later: an undeclared unbounded source pumps into the document and holds it open for as long as it produces.
The server runtime reports on the same channel, with the same in <App> › <Page> line.
Two groups.
Findings (SSR_RENDER_ERROR_CONTAINED, SSR_SUBTREE_ABANDONED, SSR_STREAM_ABANDONED, LATE_HEADER_WRITE, DYNAMIC_ASYNC_COMPONENT, SERVER_ERROR_SANITIZED, FRAME_MARKER_CORRUPTED) are facts about a render that exist in observe builds too — an APM sees them in production; in dev they print.
Checks (the rest, SSR_BOUNDARY_WATERFALL and SSR_CLIENT_CONTENT_MASKED included) are dev-only guidance.
A captured artifact from a server render carries both.
How to fix it
Declare the server function live(...) — the document then takes each source's first value and closes it, and the client connects for the rest after hydration — or bound the source.
Frame-stream renders (a live connection) are never judged.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while SSR_UNDECLARED_LIVE_SOURCE 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.