Repository navigation
fix(check-types): guard tsc -b against emitting into source tree - #22
Merged
Merged
Conversation
- fail before tsc -b when a config in the reference graph has no noEmit/outDir - fall back to tsc --noEmit on malformed tsconfig (TS Debug Failure on Windows paths) - registry test for per-cwd command resolution - README: tsbuildinfo note
robdmoore
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #21.
check-typesusestsc -b, it first reads every config in the reference graph (withextendsapplied, no file globbing; ~5 ms). If any config with inputs has nonoEmit,outDiroroutFile, the check fails with the offending configs and the fix, instead oftsc -bwriting.jsnext to the source. The Vite template and composite builds intooutDirpass.ts.readConfigFilethrew an internalDebug Failureon backslash paths when the tsconfig had a syntax error. Paths are now forward-slashed and read errors fall back totsc --noEmit, so tsc reports the real syntax error..tsbuildinfo:tsc -brejects--tsBuildInfoFile/--outDiron the CLI (TS5094), so it can't be suppressed. README and the guard message point totsBuildInfoFileundernode_modules/.tmp.Verification
include+referencesand nonoEmit:verifyx check-typesfails with the message and writes no files (previously wrotesrc/a.js).