Fix --showConfig to show transitively implied options that vary from the default config
#60240
Conversation
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
typescript-bot
added
Author: Team
For Milestone Bug
jakebailey
reviewed
Oct 16, 2024
jakebailey
approved these changes
Oct 16, 2024
jakebailey
approved these changes
Oct 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #59442
#56701 made it so
--showConfigshows implied compiler options if their implied value differs from what you’d get with no config. However, it mistakenly only showed implied options that were affected by an explicitly set option, while failing to show implied options that were affected by other implied options. For example, setting--module nodenextimplies--moduleResolution nodenext, which implies--resolvePackageJsonExports. But--resolvePackageJsonExportspreviously didn’t show up with--module nodenext --showConfig.