add expo sdk 53 support #10
Draft
+9,107
−12,892
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
|
any idea how to build the studio.js based on React 19? |
|
@Kyrylo-Usichenko sorry to ping you directly. do you know how to build the |
|
+1 person are looking for this PR to be merged, haha. Thank you guys |
|
+1 |
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.
Why
Expo SDK 53 introduces a breaking change in the devtools client transportation. We have to rebuild the webui from SDK 53.
How
build:all,web:exportscripts fornpx expo exportcannot output directory out of project root.unstable_enablePackageExportsis enabled by default.Cannot read properties of undefined (reading 'ReactCurrentOwner')