WIDE_SCOPE_DEPS
Scope subscribed to 200+ sources (attribution cost checks on).
What you saw
- Kind:
perf - Severity:
warn(code that works but is structurally wrong or expensive)
The console report opens with [WIDE_SCOPE_DEPS] 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: "WIDE_SCOPE_DEPS", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
Attribution engine cost checks only: a scope is subscribed to 200 or more sources (it re-warns on 50% further growth).
HMR plumbing sources are not counted, and in dev the renderer's insert child-resolution pass (which tracks each row's resolved child) is not judged — HUGE_FAN_IN still is.
These fire only while attribution is enabled and describe cost, not incorrect behavior. The numbers in the message are measurements, not guesses.
How to fix it
The message lists up to 12 of them — start there, and narrow the reads or split the scope as described under HUGE_FAN_IN.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while WIDE_SCOPE_DEPS is among them, with the events as evidence; after the fix, the code is gone from artifact.diagnostics.
expectRerunBudget(artifact, max, { scope }) bounds how often a named scope may re-run, and expectNoWaste(artifact) fails on re-runs whose result was unchanged.
Both read the attribution records, which captureArtifact collects unless attribution: false is passed.
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.
- Attribution: the engine whose records explain a re-run, a hold, or a waterfall.