New Architecture upgrade: dependency guidance
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react-native
- Domain
- documentation, mobile-dev
Research direction
Start with the linked new-architecture-app-intro page and compare its current guidance with the question in this issue. Update the documentation to clarify the dependency requirement before switching and address whether a tool or command can help developers check compatibility.
Written by the indexing model from the issue text.
Description
Description
Improve the documentation concerning if my dependencies need to support the new architecture before I can switch.
What is the problem?
It is unclear to me if all my dependencies with Native code need to support the new architecture before I can switch my app across.
While the docs don't mention this one way or the other, there is much discussion across the ecosystem about new libraries moving to the new architecture.
How can we address it?
Add a section to https://reactnative.dev/docs/next/new-architecture-app-intro clarifying. If you need everything to support the new architecture, it would be great if there was a tool or command I could use to check this easily.
Why is it important?
Save time and questions from the community when they try to switch
Who needs this?
App developers
When should this happen (use version numbers if needed)?
By 0.70 preferably as it feels like that's going to have a big New Architecture push.
- Dominant language
- MDX
- Stars
- 2.2k
- Forks
- 6.3k
- Avg merge
- 11h 37m
- Merged PRs (30d)
- 19
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from react/react-native-website
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
react/react-native-website#5217 ·
-
Integration with Existing Apps: Podfile example does not use `use_react_native!`, is incomplete Open👋 Good first issue
Difficulty 1/5 Under an hour Newbie friendliness 78/100
react/react-native-website#2958 · 2 comments ·
-
:ghost: Missing Docs 👋 Good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
react/react-native-website#889 · 5 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
react/react-native-website#5216 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
react/react-native-website#5154 · 6 comments ·
All issues in react/react-native-website
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100