docs: clarify tsconfig resolution behavior#21179
Merged
sapphi-red merged 3 commits intoDec 2, 2025
Merged
Conversation
bluwy
reviewed
Dec 2, 2025
Co-authored-by: Bjorn Lu <bjornlu.dev@gmail.com>
bluwy
approved these changes
Dec 2, 2025
Member
I did some checks again and I notice that if the nearest tsconfig.json, even if it didn't include the file, but other files that are included import that file, the tsconfig would also apply to that file too. So I guess this makes the compatibility even more complex, not quite sure how to handle that. |
Member
Author
|
Oh, that's a weird behavior. I guess it's fine for now as long as the cases where the files are included. |
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.
Clarified how the tsconfigs are resolved and which field are respected.
Thought about clarifying this while working on vitejs#529