chore: upgrade to Expo SDK 58 canary - #32
Draft
janicduplessis wants to merge 2 commits into
Draft
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
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.
Description
Upgrade Trailhead to the pinned Expo SDK 58 canary / React Native 0.87 stack for the next benchmark campaign. This remains a canary dependency set, not a stable SDK release, and does not by itself fix cross-worktree C++ cache misses.
Solution
Use compatible native-library versions where the canary recommendations fail to build, and keep those overrides explicit so
expo install --fixdoes not undo them. Scoped npm peer overrides and Worklets' explicit Metro dependency make the regenerated lockfile installable without ignoring peer dependencies.Build only ExpoVideo from source on iOS: the canary's prebuilt framework aborts at launch with
Library not loaded: @rpath/Testing.framework/Testing. Other prebuilt Expo modules remain enabled. Keep both committed native projects rather than regenerating them.Test plan
npm ci, fullnpm ls --all,expo install --check, Expo Doctor, typecheck, lint, and Android Metro export.