Regression in 0.0.10: switching to Node AbortController/AbortSignal breaks Jest tests with AggregateError

[daveobrien-optaxe]

Upgrading jest-fixed-jsdom from 0.0.9 to 0.0.10 causes widespread test failures (AggregateError during render/act) on our repo. Rolling back to 0.0.9 fixes all failures. The only change in 0.0.10 appears to be using Node’s global AbortController/AbortSignal, which likely changes abort/error semantics in the test environment.

Reference: compare v0.0.9…v0.0.10

Environment

• Node: 22.11.0
• Jest: 29.7.0
• testEnvironment: jest-fixed-jsdom
• @testing-library/react: 16.0.0

Reproduction

1. Set testEnvironment: jest-fixed-jsdom in jest.config.ts.
2. Install jest-fixed-jsdom@0.0.10.
3. Run tests that render React components which internally use fetch/Relay or abortable operations.
4. Observe failures - Example failure snippet (one of many):

AggregateError:

  at aggregateErrors (node_modules/react/cjs/react.development.js:527:11)
  at act (node_modules/react/cjs/react.development.js:873:24)
  at render (node_modules/@testing-library/react/dist/pure.js:292:10)

Notes

• I’m not certain whether the root cause is specifically React 19’s act handling or error propagation from the environment; I only observe the regression coinciding with the Node AbortController/AbortSignal switch in 0.0.10.
• There’s an open issue that may be related to global overrides breaking tests: see “Always overriding global value breaks some tests” 1.

Ask

• Could you confirm whether the Node AbortController/AbortSignal swap is intended to be unconditional?
• If so, is there a recommended way to opt-out or align error/abort semantics with JSDOM’s DOM-style APIs to avoid these regressions?

Thanks

[robinzigmond]

I'm seeing what I think is a related error:

TypeError: Failed to execute 'addEventListener' on 'EventTarget': parameter 3 dictionary has member 'signal' that is not of type 'AbortSignal'.

This appears to be because although jest-fixed-jsdom now uses the native NodeJS AbortSignal type, it doesn't make any changes to jest-environment-jsdom's AddEventListener implementation which is still taken from jsdom, and expects the AbortSignal type to match its own.

Reverting jest-fixed-jsdom to version 0.0.9 fixes this problem.