Upgrade to React 19.0.0 and React Native 0.79.5 #315
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
workflow: benchmarks/sizeComparison of minified (terser) and compressed (brotli) size results, measured in bytes. Smaller is better.
|
necolas
force-pushed
the
react-19-update
branch
2 times, most recently
from
06fa166 to
da1cc48
Compare
workflow: benchmarks/perf (native)Comparison of performance test results, measured in operations per second. Larger is better.
|
Contributor
Author
|
Fix for RN flow types facebook/react-native#51908 |
This was referenced Jun 13, 2025
Contributor
|
🎉 RN 0.79.4 is available and fixes the issue with Flow types |
Contributor
Author
|
0.79.4 is still broken New pick request for 0.79.5 should fix it reactwg/react-native-releases#1000 |
Ignore react-test-renderer deprecation warnings for now. Close #300
React Native removed the 'experimental_layoutConformance' prop from View and introduced the 'experimental_LayoutConformance' component. This new component is expected to wrap any tree that needs to opt into W3C layout. Use of the new component now requires explicit setting of a prop on 'html.*' elements - 'data-layoutconformance="strict"'. This is done to avoid wrapping every `View` in a `LayoutConformance` component, since that now alters the component tree rather than just adding a prop. Adding a prop to RSD elements is also preferred because it avoids two other problems: 1) Developers having to import from 'react-native' in a file that might otherwise be expected to be cross-platform, 2) React Native for Web having to add support for this export to avoid crashing Expo apps (unless using file forks.) The use of another special 'data-*' attribute avoids React DOM warnings about unrecognized properties on web. Fix #245
Replace the polyfills with the built-in support for `marginInline`, etc. Close #219
We can't tell jest to ignore certain branches for coverage purposes because the hermes parser removes the necessary code comments. facebook/hermes#1098
necolas
changed the title
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.
This diff bumps the dep requirements to React Native 0.79.5 and React 19.0.0 (can't use 19.1.0 with React Native 0.79.5).
There is also a change to how React Native is configured to use W3C layout conformance. This can no longer be done automatically by RSD and requires the use of a special prop on the root
htmlelement of the app, which will render the necessary React Native component behind the scenes. On web, nothing happens.Some unit tests are also modified to check for RSD-specific warnings and errors, to work around the increase in errors caused by the upgrade to react-test-renderer, which is deprecated for React 19. However, there is no good cross-platform testing alternative at this stage, with the React recommended 3P libraries having incompatible APIs.