-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade TypeScript, Jest, Prettier, etc. to modern versions #176
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@@ -14,7 +14,7 @@ jobs: | |||
|
|||
strategy: | |||
matrix: | |||
node-version: [8.x, 10.x, 12.x] | |||
node-version: [10.x, 12.x, 14.x] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're dropping support for older node versions, this new requirement should also be updated on the "engines" section of the package.json file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO we should probably also bump the major package version.
Curious what the timeframe might be for getting this merged and released? |
What problem does this PR solve?
I found that my code wouldn't compile when using modern TS syntax (e.g.
?.
and??
were not available). Upgrading TS required upgrading the rest of the dev environment stack.What does this PR do?
The versions of the dev dependencies were very old, so I updated them to the latest versions. I ran the linter and fixed the new issues
What testing was done?
Ran UTs.