Align tsconfig.json with TypeScript 4.4+ #270
Merged
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
emin93
approved these changes
May 18, 2022
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.
This aligns
tsconfig.jsonwith the default as generated bytsc --init(using TypeScript 4.6.4).TypeScript has updated the format (mainly ordering and documentation) of
tsconfig.jsonstarting with TypeScript 4.4While there are many line changes, there are zero configuration changes: The values for
target,module,lib, etc. remain the same - Any potential future updates should be done in a separate PR, not mixed with a (primarily) visual formatting change.The only new option added (which TS now includes by default), is
"forceConsistentCasingInFileNames": true, which I think is good to have.Adding a
// prettier-ignorecomment at line 1 of the file ensures Prettier does not accidentally reformat the whole file, resulting in misalignment of documentation comments on non-commented lines only.