Repository navigation
fix(compiler-cli): do not treat declaration files as compilation roots in preprocessor - #71428
Merged
Merged
Conversation
…s in preprocessor Declaration files listed in a tsconfig's `files` (every transitive dependency, in Bazel-style builds) were analyzed as roots, processed and streamed to the host, which then emitted `.d.ng.ts`/`.d.ng.ts.map`/`.d.ngtypecheck.ts` next to each of them. This can end up consuming a lot of memory and potentially exhaust some targets.
JeanMeche
approved these changes
Oct 19, 2026
Member
Author
|
This PR was merged into the repository. The changes were merged into the following branches:
|
This was referenced Oct 19, 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
2 participants
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.
Declaration files listed in a tsconfig's
files(every transitive dependency, in Bazel-style builds) were analyzed as roots, processed and streamed to the host, which then emitted.d.ng.ts/.d.ng.ts.map/.d.ngtypecheck.tsnext to each of them. This can end up consuming a lot of memory and potentially exhaust some targets.