-
Notifications
You must be signed in to change notification settings - Fork 207
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
TypeScript 5.1 #7822
TypeScript 5.1 #7822
Conversation
I'm not clear on what our purposes are. Help?
I looked at that issue briefly; it's not clear to me how it helps us. #7534 says
I don't see a problem with 4.7. |
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.
I don't understand the motivation well enough to approve.
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.
Thanks for keeping up with this. Since it took me this long to come around reviewing it, let's go all the way to 5.1. Also especially with parsers, I'd prefer if we could dedup the deps and effectively bump the version instead of adding a newer version.
In general we should keep up with newer revisions of TS. Besides bug fixes and improvements, it makes it more likely that the code editor will be using the same version in its language server (if using the default configuration to use the built-in version instead of repo specific version). |
a3c8de0
to
97e8029
Compare
closes: #7534
supersedes: #6578
Description
Upgrade TypeScript to 5.1.6. Release notes for 5.1:
https://devblogs.microsoft.com/typescript/announcing-typescript-5-1/
5.1.6 fixes a regression with typescript-eslint: typescript-eslint/typescript-eslint#6934
A key benefit to upgrading is getting @satisfies This doesn't yet adopt that because it will require some changes to the jsdoc linting too.
Security Considerations
n/a
Scaling Considerations
n/a
Documentation Considerations
n/a
Testing Considerations
CI