Repository navigation
chore: upgrade React Native to 0.83 - #682
Merged
Merged
Conversation
Bump react-native to 0.83.10 (React 19.2), react-native-macos and react-native-windows to 0.83, and react-native-test-app to 5.4. RN 0.83.5+ ships fmt 12.1.0, which builds on Xcode 26, so the iOS and macOS CI jobs go back to macos-latest without the Xcode 16.2 pin. Example app: - Drop the local node_modules/react-native/android maven repo, which RN no longer ships. - Gradle wrapper 8.8 -> 9.0.0. Flow: - flow-bin 0.222 -> 0.289 (the version RN 0.83 uses), with the matching .flowconfig options. - Type-only fixes for removed/renamed types (SyntheticEvent, HostComponent, React.AbstractComponent, Element) and error codes on every suppression. No runtime changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Naturalclar
force-pushed
the
spike/rn-0.83-xcode26
branch
from
November 16, 2026 04:57
780e64f to
d2d7936
Compare
Naturalclar
marked this pull request as ready for review
November 16, 2026 04:57
The RN 0.83 version bump accidentally overwrote the top-level
"react-native" entry field ("js/index.js" -> "0.83.10") and pinned
peerDependencies to react 19.2.0 / react-native 0.83.10. Restore both.
Example app (found by running it on a simulator/emulator; CI only
compiles native code and never starts Metro):
- @rnx-kit/metro-config ^2.0.0 -> ^2.2.6; 2.0.1 crashes on Metro 0.83
("exclusionList is not a function").
- Resolve @react-native-picker/picker to the library's source in
metro.config.js. The library is the root workspace, which Yarn does
not link into node_modules, so the example could not bundle.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 tasks
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.
Upgrades React Native from 0.76 to 0.83 in one step. This removes the Xcode 16.2 pin #680 added: RN 0.83.5+ ships
fmt12.1.0, which builds on Xcode 26, so the iOS and macOS jobs go back tomacos-latest.The library's native code (iOS, Android, macOS) compiles on 0.83 with no changes. Everything below is dependency, example-app or tooling setup.
Changes
react-native0.83.10,react/react-test-renderer19.2.0,react-native-macos/react-native-windows^0.83.0,react-native-test-app^5.4.17,@react-native/*0.83.10,@react-native-community/cli*20.0.0macos-latest; Xcode 16.2 pin removednode_modules/react-native/androidmaven repo lookup (RN no longer ships it); Gradle wrapper 8.8 → 9.0.0flow-bin0.222 → ^0.289 (what RN 0.83 uses) plus the matching.flowconfigoptions@rnx-kit/metro-config^2.2.6 (2.0.1 crashes on Metro 0.83);metro.config.jsresolves@react-native-picker/pickerto the library source, since Yarn doesn't link the root workspace intonode_modulesjs/SyntheticEvent→NativeSyntheticEvent,HostComponentnow imported fromreact-native,React.AbstractComponent→React.ComponentType, and every$FlowFixMenow has an error code. No runtime changes.Runtime check
Ran the example app with Metro locally:
Running the app turned up three problems CI can't see, all fixed in the second commit: the version bump had overwritten the package's
"react-native"entry field and pinned thepeerDependencies, and the example couldn't start or bundle in Metro.Not covered
Deprecation warnings: RN 0.83 warns about deep imports (
react-native/Libraries/Utilities/codegenNativeComponent/codegenNativeCommands) injs/Android*NativeComponent.js. Harmless for now. Follow-up.Old architecture: RN 0.82+ only runs the New Architecture, so the library's old-arch code paths are no longer exercised by CI.
macOS:
react-native-test-app5.4 officially listsreact-native-macosup to 0.81. 0.83.0 builds fine in CI despite the peer warning.Jest:
yarn test:jestwas already broken before this PR (Jest 26 vs RN's Jest 29 environment) and is still broken. Follow-up.🤖 Generated with Claude Code