Use features for selected module resolution rather than all features … #47007
+190
−3
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.
…for type reference directives, since they can add restrictions to resolutions (eg,
exports
that don't contain atypes
resolution and no adjacent declaration files to the js ones blocking use of a top-leveltypes
field). This should prevent the new module resolution features from affecting people who don't opt-in to them via the new module modes (though I'm pleased with how quickly it seems some of the affected packages reacted to add atypes
entry to their exports!).Fixes #46860
cc @DanielRosenwasser because I imagine you'll want to backport this to 4.5