Summary
On a moduleResolution: bundler project using effect@4.0.0-beta.88, effect-language-service diagnostics --project tsconfig.json reports Checked 3 files out of 27 and 0 findings, while overview --project on the same tsconfig processes all 27 files and resolves the full Effect surface (144 yieldable errors, Schema classes, etc.). The analyzer can clearly see the files; the diagnostics file-selection under-reports.
Impact
CLI-driven per-edit workflows (e.g. an editor/agent hook running diagnostics --file <path>) silently miss diagnostics on most files. Patched-tsc doesn't have this problem — it flags across the whole program — which is a good workaround but means the standalone diagnostics CLI can't be trusted as the sole gate.
Repro shape
- effect:
4.0.0-beta.88; ELS: 0.86.4
- tsconfig:
moduleResolution: bundler, a paths remap of effect → a single .d.ts, plus a few external files in include (cross-project contract files).
diagnostics --project and diagnostics --file <any-in-project> → Checked 3 files out of 27.overview --project on the same config → processes 27/27.
Removing the paths remap did not change the count, so it looks tied to project-file selection rather than module resolution. Is the diagnostics file set intended to differ from overview's? I can put together a minimal repro repo if useful.
Summary
On a
moduleResolution: bundlerproject usingeffect@4.0.0-beta.88,effect-language-service diagnostics --project tsconfig.jsonreportsChecked 3 files out of 27and 0 findings, whileoverview --projecton the same tsconfig processes all 27 files and resolves the full Effect surface (144 yieldable errors, Schema classes, etc.). The analyzer can clearly see the files; thediagnosticsfile-selection under-reports.Impact
CLI-driven per-edit workflows (e.g. an editor/agent hook running
diagnostics --file <path>) silently miss diagnostics on most files. Patched-tscdoesn't have this problem — it flags across the whole program — which is a good workaround but means the standalonediagnosticsCLI can't be trusted as the sole gate.Repro shape
4.0.0-beta.88; ELS:0.86.4moduleResolution: bundler, apathsremap ofeffect→ a single.d.ts, plus a few external files ininclude(cross-project contract files).diagnostics --projectanddiagnostics --file <any-in-project>→Checked 3 files out of 27.overview --projecton the same config → processes 27/27.Removing the
pathsremap did not change the count, so it looks tied to project-file selection rather than module resolution. Is thediagnosticsfile set intended to differ fromoverview's? I can put together a minimal repro repo if useful.