getDocument hangs in Jest/JSDom environment

On PDF.js 2.0.385 and later, running the following simplest example:

pdf.getDocument({ data: arrayBufferData })
  .then(() => console.log('Success'))
  .catch() => console.log('Fail'));

runs fine on Node.js, obviously.

Running the same piece in Jest, as in this example (simplified, please ignore the fact the tests should be async):

describe('Test', () => {
  it('does something', () => {
    pdf.getDocument({ data: arrayBufferData })
      .then(() => console.log('Success'))
      .catch() => console.log('Fail'));
  });
}

• if testEnvironment is set to "node", succeeds.
• if testEnvironment is set to "jsdom" (default), hangs and never reaches .then().

On PDF.js 2.0.305 and earlier this is not an issue, because you can easily disable workers manually.

Now that there’s no way of doing that via config as of #9385, all projects using PDF.js and Jest/JSDom will be unable to test anything PDF.js-related. Switching testEnvironment to "node" is usually not an option as this will cause virtually everything else on front-end to fail.

[wojtekmaj]

I’ve managed to deal with it! For those stuck like me, do NOT set pdfjs.GlobalWorkerOptions.workerSrc or pdfjs.GlobalWorkerOptions.workerPort. Instead, use pdf.worker.entry.js file - simply import it and you’re done!

[p-mcgowan]

The above solution didn’t work for me, instead I had to configure jest to use node instead of jsdom (enabled by default)

Adding this to the top of my spec file solved it

/**
 * @jest-environment node
 */