Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"ReferenceError: AbortSignal is not defined" during jest execution

See original GitHub issue

Bug Description

When I try to run with jest a test suite that uses a file that import undici I get this error

ReferenceError: AbortSignal is not defined

  at Object.<anonymous> (../node_modules/undici/lib/fetch/request.js:839:3)
  at Object.<anonymous> (../node_modules/undici/index.js:94:28)

Reproducible By

Create a basic jest configuration with testEnvironment: 'node', Create a js file that imports the undici library Create a spec file to test somthing exported from that file Run jest

Expected Behavior

To not throw that exception

Environment

Node v16.14.0 Jest v27.2.1

Additional context

Googling the error I found out that another lib had to solve a similar issue. They think it’s related on how jest is mocking AbortSignal and AbortController.

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:15 (8 by maintainers)

Top GitHub Comments

1reaction

dios-davidcommented, Nov 4, 2022

fyi I updated to latest jest (29) and undici works fine with the node test environment

1reaction

feugycommented, Sep 16, 2022

I couldn’t come up with an easy reproduction. The mono-repo where it’s happening is quite big, and there are surely side-effects which result in this error. What I can tell for sure, is that undici and fetch are working absolutely fine on a ts/js projects with ESM.