'ReferenceError: AbortSignal is not defined' during jest execution

[D-2-G-8]

Fixes #1557

[mcollina]

@DariaGritsienko thanks for opening this! #2021 seems already fixed, are you sure you linked to the right PR?

[D-2-G-8]

yes, thanks, fixed it - #1557
@mcollina

[mcollina]

lgtm, let's see if this works!

[D-2-G-8]

I studied this question a little more and found that jest adds in the jest-environment-node package global values, and they fixed it to auto in https://github.com/facebook/jest/pull/12642/files (v28.0.0)

const contextGlobals = new Set(Object.getOwnPropertyNames(global)); for (const nodeGlobalsKey of nodeGlobals) { if (!contextGlobals.has(nodeGlobalsKey)) { // @ts-expect-error global[nodeGlobalsKey] = globalThis[nodeGlobalsKey]; } }

I think undiсi will be better without this code... :)

if people run into this problem they will need to install jest-environment-node package version >=28.0.0 and update jest >=28.0.0

I'll go try to update jest in my project, if anything else I'll be back

@mcollina