-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
chore: bump TypeScript to v5.5 #31532
Conversation
We want to make sure that our exposed @playwright/test types work with the latest TypeScript version and didn't introduce unwanted regressions. Also this release offers a lot of great enhancements which should make our developer experience better: https://devblogs.microsoft.com/typescript/announcing-typescript-5-5/
@@ -282,16 +282,16 @@ export async function convertInputFiles(files: string | FilePayload | string[] | | |||
if (!items.every(item => typeof item === 'string')) | |||
throw new Error('File paths cannot be mixed with buffers'); | |||
|
|||
const [localPaths, localDirectory] = await resolvePathsAndDirectoryForInputFiles(items as string[]); | |||
const [localPaths, localDirectory] = await resolvePathsAndDirectoryForInputFiles(items); |
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.
This is one of the highlights in this TypeScript v5.5 release. That filter will have the filter'ed type.
This comment has been minimized.
This comment has been minimized.
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.
lgtm modulo the auto-override case
Test results for "tests 1"7 flaky28423 passed, 654 skipped Merge workflow run. |
… support TS 5.5 Regressed in microsoft#31532. The TS5.5 changes broke chaining of `extend`s where the first `extend` did not specify any type arguments. Fixes microsoft#32056.
We want to make sure that our exposed @playwright/test types work with the latest TypeScript version and didn't introduce unwanted regressions. Also this release offers a lot of great enhancements which should make our developer experience better: https://devblogs.microsoft.com/typescript/announcing-typescript-5-5/