fetch errors when providing an abort signal

[tatethurston]

Version

18.14.2

Platform

Darwin c889f3b32dab 22.3.0 Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000 arm64 arm Darwin

Subsystem

No response

What steps will reproduce the bug?

Providing an instance of AbortSignal to fetch:

fetch("some url", { signal: AbortSignal.timeout(1500) })

How often does it reproduce? Is there a required condition?

Always

What is the expected behavior?

Using fetch's signal does not error. This is the behavior in 18.14.0.

What do you see instead?

An error is raised:

The "emitter" argument must be an instance of EventEmitter or EventTarget. Received an instance of AbortSignal

Additional information

Related issues:

• "MaxListenersExceededWarning: Possible EventTarget memory leak detected" from fetch with AbortSignal #46525
• [Bug]: Type error with newest node version 19.6.1 due to update of undici to version 5.19.1  remix-run/react-router#10118

[tatethurston]

Looking through the linked issues, the underlying issue seems to be fixed and this will be resolved when node 18.14.3 is available. Posting this primarily to save someone else some debugging and searching cycles.

[tatethurston]

Digging in further here, this only reproduces with nextjs on v 18.14.2. I'll follow up over there.

[camsjams]

This occurs when using Node 18.14.2 or greater, not just on nextjs.

See also nodejs/undici#1910 (comment)

Can you reopen please @tatethurston

[aduh95]

Do you still see the issue on v18.16.0?

[benjamingr]

An AbortSignal is an EventTarget - are you using the built in AbortSignal or something else?

[houfeng0923]

v18.15.0 has.
it caused the cases related fetch can't pass.
v20.9 is ok