SYNC_NODE_RECEIVED_ASYNC
sync: true computation returned a Promise / AsyncIterable.
What you saw
- Kind:
lifecycle - Severity:
error(broken behavior)
The console report opens with [SYNC_NODE_RECEIVED_ASYNC] 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: "SYNC_NODE_RECEIVED_ASYNC", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
A computed/effect created with sync: true returned a Promise or AsyncIterable; the value would be stored as-is, never awaited, in production.
How to fix it
Remove sync: true to use async-aware behavior, or unwrap before returning.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while SYNC_NODE_RECEIVED_ASYNC 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.