UNSCOPED_HOLE_ALLOCATED_IDS
Unscoped hole was handed a function whose content took ids at a position the other side does not share; keys permute (dev).
What you saw
- Kind:
render - Severity:
warn(code that works but is structurally wrong or expensive)
The console report opens with [UNSCOPED_HOLE_ALLOCATED_IDS] 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: "UNSCOPED_HOLE_ALLOCATED_IDS", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
A JSX hole was handed a function (data.name) instead of a value — const renderHead = () => props.header; <div>{renderHead}</div> — and calling it built hydratable content.
The compiler scopes every hole that could build JSX so server and client agree on hydration ids, but a bare identifier bound to a function is a value to the compiler and a thunk to the runtime: unscoped, its content takes ids from the enclosing counter where each side happens to evaluate it — the client at the statement, the server in the walk after the scoped holes that follow it reserved theirs — and the keys of its content and of the holes after it permute: detached copies on hydration, dead handlers.
A function hole with nothing scoped after it lands on the same ids both sides and is silent; the finding is the shift.
The server reports it structurally (data.registered ≠ data.before, the counter's next id when the hole was registered vs. evaluated; data.after after it ran), the client when the content it built in place (data.before → data.after) missed a server-rendered key.
Once per site.
JSX.Element excludes functions, so this shape is reached only from JavaScript or through a cast.
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
Fix: call the function at the hole ({renderHead()} — a call hole is scoped on both sides) or assign the built value first and insert that.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while UNSCOPED_HOLE_ALLOCATED_IDS 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.