docs(tsconfig): align reference resolution docs with TypeScript behavior#9641
Merged
shulaoda merged 3 commits intoJun 3, 2026
Conversation
✅ Deploy Preview for rolldown-rs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…on_docs_with_typescript_behavior
IWANABETHATGUY
approved these changes
Jun 3, 2026
shulaoda
deleted the
06-03-docs_tsconfig_align_reference_resolution_docs_with_typescript_behavior
branch
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.
What
Updates
packages/rolldown/src/options/docs/tsconfig.mdto describe how a tsconfig'sreferencesare resolved as of v1.1.0. Docs-only, no behavior or code change.Why
The reference resolution behavior changed in v1.1.0 through the
oxc_resolverupgrades:oxc_resolver→11.20.0) brought in oxc-resolver #1151: a referenced project that includes the file takes precedence over the root, instead of the root claiming it first.oxc_resolver→11.21.0) brought in oxc-resolver #1198: whether a.js/.jsx/.mjs/.cjsfile is included is decided by each referenced project's ownallowJs, not the root's.The existing docs still described the previous model (root matches first, references consulted only as a fallback), which no longer holds. A solution-style
tsconfig.json(onlyreferences, as Vite scaffolds) now resolves the way TypeScript does, which is also what made the standard Vitepathsaliases resolve correctly again (#8468).Changes
referencesresolution paragraph: a referenced project that includes the file takes precedence over the root, each referenced project uses its ownallowJs(so a.js/.jsx/.mjs/.cjsfile is only included where that project enables it), and the root is used only when no referenced project includes the file.