Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Architecture upgrade: dependency guidance #3275

Open
johnf opened this issue Aug 22, 2022 · 6 comments
Open

New Architecture upgrade: dependency guidance #3275

johnf opened this issue Aug 22, 2022 · 6 comments
Labels
Never gets stale Prevent issues/PRs from getting stale

Comments

@johnf
Copy link
Contributor

johnf commented Aug 22, 2022

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.

@cortinico
Copy link
Contributor

it would be great if there was a tool or command I could use to check this easily.

This is discussed here microsoft/rnx-kit#1863
Please share your insights over there as we design this tool.

As for the docs, I also believe we're not clear on this point and we should potentially clarify it more (cc @cipolleschi @rickhanlonii)

@github-actions
Copy link

github-actions bot commented Dec 8, 2022

👋 Hey there, it looks like there has been no activity on this issue in the last 90 days. Has the issue been fixed, or does it still require the community attention? This issue will be closed in the next 7 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale Issues/PR that are not getting much activity and are closer to be closed label Dec 8, 2022
@cortinico
Copy link
Contributor

Improve the documentation concerning if my dependencies need to support the new architecture before I can switch.

Reviving this.
Yes we need a page on backward compatibility similar to the work that @kelset did on https://github.com/kelset/react-native-new-arch-limits

@cortinico cortinico removed the Stale Issues/PR that are not getting much activity and are closer to be closed label Dec 8, 2022
@github-actions
Copy link

github-actions bot commented Mar 9, 2023

👋 Hey there, it looks like there has been no activity on this issue in the last 90 days. Has the issue been fixed, or does it still require the community attention? This issue will be closed in the next 7 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale Issues/PR that are not getting much activity and are closer to be closed label Mar 9, 2023
@cortinico
Copy link
Contributor

This is not stale. We'll be having this in the near future 👍

@cortinico cortinico removed the Stale Issues/PR that are not getting much activity and are closer to be closed label Mar 9, 2023
@github-actions

This comment was marked as off-topic.

@github-actions github-actions bot added the Stale Issues/PR that are not getting much activity and are closer to be closed label Jun 8, 2023
@cortinico cortinico added Never gets stale Prevent issues/PRs from getting stale and removed Stale Issues/PR that are not getting much activity and are closer to be closed labels Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Never gets stale Prevent issues/PRs from getting stale
Projects
None yet
Development

No branches or pull requests

2 participants