refactor: upgrade examples app to Expo SDK 51 #159
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a test to see what's required to upgrade to SDK 51, re:
So far, it seems that the multiple
react-nativeversions is causing trouble. Unfortunately, this is a known issue of react-native, but definitely worth looking into. The 2nd version is installed because of two things:0.xconsiders all0.xversions to be breaking changes, meaning that^0.73.ydoes not include0.74.y.react-strict-domhas a peer dependency ofreact-native: "^0.73.y, and because its not satisfied, it auto-installs this version in the monorepo.