Update TypeScript to the latest stable version #47
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 has been updated to the latest stable version. Additional TypeScript options added in these versions have been migrated into the `tsconfig.json` from the MetaMask module template. One option was kept back for now: `noUncheckedIndexedAccess`. This option resulted in too many errors, so will be attempted in a separate PR. The range was updated to use `~` because TypeScript doesn't follow SemVer; their minor releases can include breaking changes.
|
Issue created here to track adding |
rickycodes
approved these changes
Nov 8, 2022
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.
TypeScript has been updated to the latest stable version. Additional TypeScript options added in these versions have been migrated into the
tsconfig.jsonfrom the MetaMask module template.One option was kept back for now:
noUncheckedIndexedAccess. This option resulted in too many errors, so will be attempted in a separate PR.The range was updated to use
~because TypeScript doesn't follow SemVer; their minor releases can include breaking changes.