Skip to content

Conversation

@sandersn
Copy link
Contributor

Add static method AbortSignal.timeout.
If this works, a later version of TS can re-add AbortSignal.abort and node can add support for that too.

I created a ts4.8/ subdirectory for each of v14, v16, and current. I didn't try to share types like before. With 2*3 entries I think it's reasonably maintainable and the old way was very confusing to change.

typesVersions has a weird entry ">4.9.0-a": { "*": ["*"] } which works around a bug in semver parsing in Typescript. I need to ship a new version of dtslint to allow this but I wanted to get this PR out for people to look at.

Add static method AbortSignal.timeout.
If this works, a later version of TS can re-add AbortSignal.abort and
node can add support for that too.

I created a ts4.8/ subdirectory for each of v14, v16, and current. I
didn't try to share types like before. With 2*3 entries I think it's
reasonably maintainable and the old way was very confusing to change.

typesVersions has a weird entry `">4.9.0-a": { "*": ["*"] }` which
works around a bug in semver parsing in Typescript. I need to ship a new
version of dtslint to allow this but I wanted to get this PR out for
people to look at.
@sandersn sandersn changed the title Update node types for TS 4.9 Update node types for TS 4.9 beta Sep 22, 2022
@DanielRosenwasser
Copy link
Member

The semver bug is over at microsoft/TypeScript#50909 FWIW

@rbuckton
Copy link
Collaborator

The minimum prerelease version is -0, so >4.9.0-0 might be what you want.

Comment on lines 5 to 6
">4.9.0-a": { "*": ["*"] },
"<=4.8": { "*": ["ts4.8/*"] }
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
">4.9.0-a": { "*": ["*"] },
"<=4.8": { "*": ["ts4.8/*"] }
">=4.9.0-0": { "*": ["*"] },
"<4.9.0-0": { "*": ["ts4.8/*"] }

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, with "<4.9.0-0", ">=4.9.0-0" is no longer needed. I'll change dtslint to allow <=4.8 or <4.9.0-0

@sandersn
Copy link
Contributor Author

I'm going to update the format of typesVersions in dependents in a separate PR. Those are the only failures, so I'm going to merge this.

@sandersn sandersn merged commit e70b227 into master Sep 23, 2022
@sandersn sandersn deleted the node-update-ts4.9 branch September 23, 2022 17:42
@peterblazejewicz
Copy link
Member

would that impact CI validation time? Let me check

@phm07
Copy link
Contributor

phm07 commented Sep 24, 2022

#62389 fails because of this

@peterblazejewicz
Copy link
Member

@pauhull those errors with TS versioning have been fixed in master. You have to update your PR from current master

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.

6 participants