Repository navigation
Conversation
- Updated package versions in pnpm-workspace.yaml to align with Expo SDK 58. - Added new aliases for React Native subpath exports in NativeEntryPlugin tests. - Introduced setup-env.js to handle environment setup for React Native. - Enhanced documentation to clarify package exports requirements for React Native 0.87 and newer.
|
@whydidoo is attempting to deploy a commit to the Callstack Team on Vercel. A member of the Team first needs to authorize it. |
🦋 Changeset detectedLatest commit: 9242c5f The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
- Changed react-native-screens version to use testers catalog. - Updated react to 19.3.0 and react-native to 0.88.0. - Adjusted expo58 catalog to remove redundant react and react-native entries. - Updated react-native-test-app to 5.4.14. - Updated babel presets and community CLI plugins to 0.88.0. - Ensured compatibility with React Native >= 0.87 by adding metro-config. - Updated versions for react-native-reanimated, react-native-safe-area-context, react-native-screens, and react-native-worklets.
This branch has not been deployed
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.
Summary
Expo SDK 58 (React Native 0.88) didn't bundle with Re.Pack. This PR fixes it and moves the Expo testers to SDK 58.
@react-native/js-polyfills. In Expo apps it is only reachable throughexpo→@expo/metro-config, so the lookup now checks there too. RN <= 0.86 still usesrn-get-polyfills.js.react-native/setup-env,react-native/react-private-interfaceand the other subpaths RN declares inexportsdidn't resolve, becauserepack-expoaliasesreact-nativeto its directory.NativeEntryPluginnow adds exact aliases for them. It also maps@react-native/assets-registry/registry(used byreact-native-svg<= 15.15) to RN's registry. A user's own alias for the same request is never overridden.@react-native/assets-registryis aliased only whenreact-nativedepends on it. RN 0.88 dropped that dependency, so a standalone SDK 58 app failed withREACT_NATIVE_RESOLUTION_FAILED.expo57catalog becomesexpo58(expo ~58.0.13, RN 0.88.0, React 19.3.0).Test plan
repackjest 365/365,repack-expo125/125 (9 failed on SDK 58 before this PR), integration 139 passed, typecheck clean.apps/tester-expoon the iOS simulator and the Android emulator, in dev and in release (repack-expo build --run): all 7 routes work, including both MF v2 widgets and Fast Refresh.