[Bug]: jest-environment-jsdom webIDL validator issue in node 18

[MGibson1]

Version

29.6.2

Steps to reproduce

1. Clone my repo at https://github.com/mgibson1/jest-jsdom-issue
2. Install with npm ci
3. Test with npm run test
4. Observe type error (note, the type of the 2nd argument is ArrayBuffer:

TypeError: Failed to execute 'importKey' on 'SubtleCrypto': 2nd argument is not instance of ArrayBuffer, Buffer, TypedArray, or DataView.

Expected behavior

Tests should pass since parameter types match

Actual behavior

Test fails with TypeError

Additional context

Working with JSDOM

The testEnvironment-node branch changes test environment to node and injects a simple JSDOM into global.

Tests pass in this branch.

Working when using a TypedArray

the typed-array branch still uses jsdom as a test environment, but converts usage in crypto from ArrayBuffer to TypedArray. I don't see why these types would be interpreted differently by the validator, but it appears that this is a reasonable workaround.

Suggested JSDOM workaround for other v22 issues

It was suggested to override JSDOM to use the correct version for other improvements that haven't made their way in to jest-environment-jsdom yet, but I'd pegged the package to the current release and this issue persists. It must be due to some configuration happening in jest-environment-jsdom.

Environment

System:
  OS: macOS 13.4.1
  CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Binaries:
  Node: 18.17.0 - /usr/local/bin/node
  npm: 9.6.7 - /usr/local/bin/npm

[mrazauskas]

It can be you are hitting #2549. Unfortunately I have no suggestions how exactly to make it work with JSDOM.

Perhaps a custom test environment could help? For example, you could build on top of jest-environment-node-single-context and inject JSDOM. Load it via @jest-environment pragma in selected test files. Just an idea. I didn’t try that.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.