Jest Failing After Upgrade

[JoJ123]

Describe the bug

Hi,
can you imagine why some of our Test Cases are failing with the following Error:
ReferenceError: AbortSignal is not defined
after we upgrade @graphql-yoga/node from 2.12.1-canary-23a9ff8.0 to the latest release.

If we revert the upgrade all test cases are passing again.

Your Example Website or App

test

Steps to Reproduce the Bug or Issue

Upgrade

Expected behavior

Upgrade without an issue.

Screenshots or Videos

No response

Platform

Node: 16.13.0
Jest: 26.6.3

Additional context

No response

[ardatan]

Could you share more details? Stacktrace maybe?

[JoJ123]

Is this helping:

I figured out, that removing:
testEnvironment: 'node'
from the jest.config.ts helps to not throw the error, but it will destroy all the "nocks" we have recorded.

[kanziw]

With below dependencies,

graphql-yoga/common & graphql-yoga/node -> @whatwg-node/fetch@0.3.0 -> undici:5.8.0

undici access global AbortSignal

If you upgrade jest (>=v27.4.6), it might be solved. (jestjs/jest#12157)

I solve same problem by using yarn resolution (undici@4.13.0)

It's temporary solution. I'll upgrade jest version soon.

[ardatan]

We solved it in v3. You can try it out today. Let us know if you still have issues.
Check out our migration guide;
https://www.the-guild.dev/graphql/yoga-server/v3/migration/migration-from-yoga-v2