chore(devDependencies): upgrade Typescript to version 4.14.0(latest),… #228
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
… upgraded @typescript-eslint/ to versions 4.14.0(latest), and upgraded ts-jest to version 26.4.4(latest)
Closed
1 task
hartzis
approved these changes
Mar 1, 2021
This was referenced Mar 1, 2021
Closed
Closed
Merged
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.
What:
This Pull Request includes all the necessary dependency upgrades for Typescript 4.x.x to work properly.
How:
Upgrade was performed by running
yarn upgrade-interactive --latest. After upgrading Typescript version -^3.9.6 -> ^4.1.3, there were a few linting errors and warnings when building withmicrobundle. The build errors we resolved by upgrading@typescript-eslint/eslint-pluginand@typescript-eslint/parserversions -^3.6.1 -> ^4.14.0using theyarn upgrade-interactive --latestcommand again. When runningyarn test, there were a few Jest warnings. The Jest warnings were resolved by upgrading thets-jestversion -^26.1.2 -> ^26.4.4.