Skip to content
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

Merged
merged 5 commits into from
Jul 10, 2023
Merged

TypeScript 5.1 #7822

merged 5 commits into from
Jul 10, 2023

Conversation

turadg
Copy link
Member

@turadg turadg commented May 22, 2023

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

@turadg turadg requested review from mhofman and dckc May 22, 2023 16:53
@dckc
Copy link
Member

dckc commented May 22, 2023

This bumps to the RC, not release. For our purposes that's sufficient.

I'm not clear on what our purposes are. Help?

the satisfies feature: microsoft/TypeScript#51753.

I looked at that issue briefly; it's not clear to me how it helps us.

#7534 says

We've been stuck on 4.7

I don't see a problem with 4.7.

Copy link
Member

@dckc dckc left a 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.

Copy link
Member

@mhofman mhofman left a 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.

yarn.lock Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
packages/xsnap/test/test-xs-js.js Outdated Show resolved Hide resolved
@mhofman
Copy link
Member

mhofman commented Jun 2, 2023

I don't see a problem with 4.7.

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).

@turadg turadg marked this pull request as draft June 2, 2023 17:15
@turadg turadg force-pushed the typescript-5.1 branch 2 times, most recently from a3c8de0 to 97e8029 Compare July 9, 2023 21:30
@turadg turadg marked this pull request as ready for review July 10, 2023 16:05
@turadg turadg requested a review from mhofman July 10, 2023 16:05
@turadg turadg enabled auto-merge July 10, 2023 16:14
@turadg turadg added this pull request to the merge queue Jul 10, 2023
Merged via the queue into master with commit 1303537 Jul 10, 2023
@turadg turadg deleted the typescript-5.1 branch July 10, 2023 16:46
@turadg turadg mentioned this pull request Jul 10, 2023
mhofman pushed a commit that referenced this pull request Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

upgrade TypeScript to 5.1
3 participants