[Windows] @rnx-kit/preset broken with new versions of RNW
TatianaKapos opened this issue · 1 comments
TatianaKapos commented
What happened?
RNW uses @rnx-kit/preset in our CI. When trying to cut the 0.75 branch, we got errors when RNW upgraded to any react-native version above 0.75.0-nightly-20240618-5df5ed1a8 and the 0.75 release candidates.
Affected Package
@rnx-kit/jest-preset
Version
0.1.16
Which platforms are you seeing this issue on?
- Android
- iOS
- macOS
- Windows
System Information
npm WARN config This command does not support workspaces.
info Fetching system and libraries information...
System:
OS: Windows 11 10.0.22631
CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
Memory: 33.55 GB / 63.85 GB
Binaries:
Node:
version: 18.18.0
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 1.22.5
path: C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm:
version: 8.18.0
path: ~\AppData\Roaming\npm\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
AllowAllTrustedApps: Enabled
Versions:
- 10.0.17763.0
- 10.0.18362.0
- 10.0.19041.0
- 10.0.22000.0
- 10.0.22621.0
IDEs:
Android Studio: AI-213.7172.25.2113.9014738
Visual Studio:
- 16.11.34931.43 (Visual Studio Enterprise 2019)
- 17.10.35004.147 (Visual Studio Enterprise 2022)
Languages:
Java:
version: 11.0.16.1
path: C:\Program Files\Eclipse Adoptium\jdk-11.0.16.101-hotspot\bin\javac.EXE
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react: Not Found
react-native: Not Found
react-native-windows: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Steps to Reproduce
Try to use @rnx-kit/jest-preset with an RNW app above 0.75.0-nightly-20240618-5df5ed1a8 or look at the RNW 0.75.0-preview-branch https://github.com/microsoft/react-native-windows/tree/preview-0.75-test
Code of Conduct
- I agree to follow this project's Code of Conduct
TatianaKapos commented
I have my suspicions that this PR in @react-native-community/cli may be the culprit: react-native-community/cli#2379