chore(example): upgrade to Expo SDK 57 and React Native 0.86 - #141
Merged
Merged
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
1 participant
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.
The example still targets Expo SDK 55 and React Native 0.83, and its haptics dependency requires a custom native build. People looking for a working Expo Go setup in #67 cannot use that example as written. This PR updates it to stable Expo SDK 57 and its supported React Native 0.86.3, replaces the haptics dependency with
expo-haptics, and refreshes the checked-in native projects.Expo's Babel preset and splash screen plugin replace outdated configuration. The README now points Expo users to the runnable example.
Reproduction
Start the example's Expo server, open it in Expo Go on an iPhone 18 Pro simulator running iOS 27, and press Refresh. The graph renders and updates without a custom native build.