feat: add support for [email protected]
#2581
Merged
Conversation
This file contains 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
I could not get the project to compile without this file. Tried cleaning caches, nuking derived data, Pods, build directory etc. It just has to be there for some reason 🤷 I do not know also why XCode duplicates this file...
8 tasks
kkafar
added a commit
that referenced
this pull request
Dec 18, 2024
## Description #2567 introduced `ios.componentProvider` field to package definition - and that's fine, but we're pointing to wrong names there. ## Changes Updated the names to existing symbol names. ## Test code and steps to reproduce This caused runtime errors when running the app on 0.77. I need this commit for the #2581 (0.77 support) ## Checklist - [ ] Included code example that can be used to test this change - [ ] Updated TS types - [ ] Updated documentation: <!-- For adding new props to native-stack --> - [ ] https://github.com/software-mansion/react-native-screens/blob/main/guides/GUIDE_FOR_LIBRARY_AUTHORS.md - [ ] https://github.com/software-mansion/react-native-screens/blob/main/native-stack/README.md - [ ] https://github.com/software-mansion/react-native-screens/blob/main/src/types.tsx - [ ] https://github.com/software-mansion/react-native-screens/blob/main/src/native-stack/types.tsx - [ ] Ensured that CI passes
8 tasks
## Description This is required for RN 0.77 apparently. TurboReactPackage is deprecated on new arch. No idea why. I am not sure about backwards compatibility either, sorry. Feel free to close this PR if this isn't backwards compatible. <!-- Description and motivation for this PR. Include Fixes #<number> if this is fixing some issue. Fixes # . --> ## Changes <!-- Please describe things you've changed here, make a **high level** overview, if change is simple you can omit this section. For example: - Updated `about.md` docs --> <!-- ## Screenshots / GIFs Here you can add screenshots / GIFs documenting your change. You can add before / after section if you're changing some behavior. ### Before ### After --> ## Test code and steps to reproduce <!-- Please include code that can be used to test this change and short description how this example should work. This snippet should be as minimal as possible and ready to be pasted into editor (don't exclude exports or remove "not important" parts of reproduction example) --> ## Checklist - [ ] Included code example that can be used to test this change - [ ] Updated TS types - [ ] Updated documentation: <!-- For adding new props to native-stack --> - [ ] https://github.com/software-mansion/react-native-screens/blob/main/guides/GUIDE_FOR_LIBRARY_AUTHORS.md - [ ] https://github.com/software-mansion/react-native-screens/blob/main/native-stack/README.md - [ ] https://github.com/software-mansion/react-native-screens/blob/main/src/types.tsx - [ ] https://github.com/software-mansion/react-native-screens/blob/main/src/native-stack/types.tsx - [ ] Ensured that CI passes
The change is required because BaseViewManagerInterface has been removed in facebook/react-native#46809 and we need this to keep the lib working on old architecture with react-native 0.77+. This change, according to the PR is supposed to be backward compatible (older versions of react-native) should work with these new codegen specs.
I've removed dependency on gesturehandler few commits before and presence of this patch caused the CI to fail. We need to check out more recent gesturehandler versions anyway.
kkafar
commented
Dec 19, 2024
There was a problem hiding this comment.
This is not required for Fabric, as these files are auto generated there.
|
The CI does not pass due to yarn hardened mode, despite the fact that I've updated the locks in every way possible (I'm aware of) locally & pushed the changes out. Locally every build combination passes. |
|
Blocker: locally, when I enable reanimated I get following error:
(3.16.1 + patch) w/o reanimated the lib seems to be working fine, however our e2e & example apps won't work that way |
|
@vonovak Yeah, this was the culprit: https://github.com/facebook/react-native/pull/47551/files |
|
Verified that both Fabric & Paper do build & applications are functional. Let's ignore the CI. |
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
Adding support for react-native 0.77.
After this PR is merged the library will support 0.74+ Paper and 0.77 Fabric.
Please note, that I haven't notice any not-handled breaking changes - the library should work with versions down to 0.72 on old architecture and at least down to 0.76 on Fabric, however we won't extend issue resolving to these versions.
Changes
safe-area-contextto 5.0.0 (it comes with support for Paper 0.74+) in examples (not lib!),safe-area-context:Test code and steps to reproduce
When doing some quick checks I haven't noticed any obvious regressions.
Checklist