build: remove rootDir from root configuration#33137
Merged
clydin merged 1 commit intoangular:mainfrom May 6, 2026
Merged
Conversation
Removing the rootDir option from the root tsconfig.json allows the TypeScript compiler to automatically compute the root directory based on the common path of all input files. This provides more flexibility in monorepo setups where files span across multiple top-level directories like packages and modules, avoiding strict location constraints that may not apply to all build targets.
alan-agius4
approved these changes
May 6, 2026
Member
Author
|
This PR was merged into the repository. The changes were merged into the following branches:
|
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.
Removing the rootDir option from the root tsconfig.json allows the TypeScript compiler to automatically compute the root directory based on the common path of all input files. This provides more flexibility in monorepo setups where files span across multiple top-level directories like packages and modules, avoiding strict location constraints that may not apply to all build targets.