react-native-upgrade-helper sets us to ^29.2.1 here, but that should result in the same version anyways, so I figured I'd set the higher value here

Since we use jest from within lib, I figured it would be good to add this for completeness. It turns out to not actually be necessary because multiple other workspaces use this package, which results it in being hoisted to the workspace root

Jest 27 changes the default "Jest environment" from "jsdom" to "node" – see here.

In general, we want to use jsdom in the web workspace, since we depend on things like the window global in other tests. For that reason, our Jest config is updated in web/package.json below to default to jsdom.

However, using jsdom breaks this test and the next one. The issue is that jsdom doesn't yet support webcrypto.

We'd been getting around this in web/jest-setup.js by utilizing a polyfill built into recent versions of Node's crypto module (crypto.webcrypto). However, that doesn't seem to work with the jsdom environment.

Since we don't actually need any of the jsdom features, I was able to get around that by swapping this test and the next one to use the node environment. This should be fine as long as we don't have any tests that need BOTH the jsdom and node features. If we ever do, we can swap to using the external polyfill suggested here.

Jest 28 no longer includes jest-environment-jsdom, so we must install it separately ourselves

Jest 27 changes the default "Jest environment" from "jsdom" to "node" – see here.

In general, we want to use jsdom in the web workspace, since we depend on things like the window global in some tests.