[ems][jest-expo-enzyme] Deprecate the library and remove it from EMS #19777
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
We include jest-expo-enzyme in expo-module-scripts, but this library is no longer supported as of React Native 0.68 / React 18+.
jest-expo-enzyme depends on @wojtekmaj/enzyme-adapter-react-17 which in turn has a peerDependency on react@17, so the result is that when creating a new project Expo module with
npx create-expo-module
we end up with react@17 and react@18 both installed in the project. As you can imagine, this does not work very well.How
@expo/html-elements
(which also had some broken snapshot tests, so I re-recorded them because the diff looked right)Test Plan
CI
Checklist
expo prebuild
& EAS Build (eg: updated a module plugin).