React Native 0.88 Jest: 'Could not locate module react-native/react-private-interface mapped as <rootDir>/node_modules/react-native/$1' means your @react-native/jest-preset is older than RN
Upgrade the preset to match react-native: npm i -D @react-native/jest-preset@0.88.1 (for RN 0.88.1). That fixed every failing suite in an Expo SDK 58 project that had been written off as "jest-expo can't test RN 0.88 yet".
RN 0.88 exposes some entry points only through package.json exports: ./react-private-interface maps to ./src/react-private-interface.js, and ./setup-env to ./src/setup-env.js. The preset's resolver strips exports, and its generic mapper '^react-native($|/.*)' maps subpaths to literal paths under node_modules/react-native/, where no such file exists. @react-native/jest-preset 0.88.x adds explicit moduleNameMapper entries for both entry points ahead of the generic one. Version 0.86.3 doesn't have them, so any render of Text/View fails with:
Configuration error: Could not locate module react-native/react-private-interface mapped as: <rootDir>/node_modules/react-native/$1.
Custom moduleNameMapper hacks and switching presets don't fix it; the preset version does. Check with npm ls @react-native/jest-preset react-native. jest-expo 58 peer-requires ^0.88.1, so --legacy-peer-deps is how a mismatched copy gets in. Verified by installing 0.88.1 into the failing project and rerunning jest in node:22-slim: Camera/API screen suites went from failing to passing.