refactor(mobile): upgrade to Expo SDK 52 #129
Open
Conversation
This file contains hidden or 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
|
🚀 Expo preview is ready!
|
Even for pnpm, this is now fully automatic.
byCedric
force-pushed
the
@bycedric/upgrade-sdk-52
branch
from
7efd1d2 to
46e4cb3
Compare
|
Any chance you can merge this? Thank you |
|
It would be very nice to see an update of this with the current expo 52 version. Also, should the README.md file be updated? Specifically the 3. point here: https://github.com/byCedric/expo-monorepo-example?tab=readme-ov-file#pnpm-workarounds |
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.
Linked issue
We can finally drop the custom monorepo config from
metro.config.js, even for pnpm this is now automatic. Read more: https://docs.expo.dev/guides/monorepos/