[Bug]: Jest 28 with jest-environment-jsdom use browser’s version of Nano ID but does not have crypto polyfill

[ai]

Version

28

Steps to reproduce

Jest config:

export default {
  testEnvironment: 'jsdom'
};

Add to any test:

import { nanoid } from 'nanoid'

it('works with crypto', () => {
  nanoid()
})

Expected behavior

1. Use Node.js version (avoid package.exports.browser in resolver)
2. Or provide a crypto polyfill in jest-environment-jsdom

Actual behavior

Error:

ReferenceError: crypto is not defined

Additional context

Nano ID has in it’s package.json:

"exports": {
    ".": {
      "browser": "./index.browser.js",
      "default": "./index.js"
    }
  }

Seems like jest-environment-jsdom is changing the resolver to use exports.*.browser but do not provide true browser environment to make it safe.

Environment

System:
    OS: Linux 5.18 Fedora Linux 36 (Workstation Edition)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  Binaries:
    Node: 18.3.0 - ~/.asdf/installs/nodejs/18.3.0/bin/node
    Yarn: 1.22.19 - ~/.asdf/shims/yarn
    npm: 8.11.0 - ~/.asdf/plugins/nodejs/shims/npm
  npmPackages:
    jest: ^28.1.1 => 28.1.1

[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.

[SimenB]

JSDOM provides all APIs, not Jest itself, so this issue should go there (see discussion in uuidjs/uuid#616).

---

That said, JSDOM implements crypto.getRandomValues() as of https://github.com/jsdom/jsdom/releases/tag/20.0.0

[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.