[node] add AbortSignal.any()

[atlowChemi]

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change.
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm test <package to test>.

Select one of these and delete the others:

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes: nodejs/node@b1828b325e
• If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the header.

[atlowChemi]

Hi @eps1lon @peterblazejewicz 🙂
I have the UT failing for me, I assume it is because the types are not yet added to lib.dom.d.ts?
What can be done in this case?

[atlowChemi]

seems to be broken since types lack in https://github.com/microsoft/TypeScript/blob/d027e9619fb8ca964df3885a536a67b5f813738b/src/lib/dom.generated.d.ts#L2319-L2326

[ghost]

@jakebailey this can be closed

[jakebailey]

Why? I don't see this function in the current package.

[ghost]

Why? I don't see this function in the current package.

My bad, I saw something else. Should I create a PR to supersede this?

[jakebailey]

I don't really know anything about this PR, so I have no clue.

[maxdavidson]

Suggested change

	any(signals: AbortSignal[]): AbortSignal;
	any(signals: readonly AbortSignal[]): AbortSignal;

[Resetand]

Any updates?

[atlowChemi]

Any updates?

@Resetand unfortunately the dom.generated.d.ts was last updated 3 months ago, without the any function...
I'll have a look at this PR later today again to see if there is anything I can do

[atlowChemi]

Opened an issue on TypeScript repo: microsoft/TypeScript#58026

[benasher44]

With TS 5.5 out, I think this can be revived?