Skip to content

New Architecture upgrade: dependency guidance #3275

Open

Description

@johnf

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.

Activity

  1. cortinico commented on Sep 8, 2022

    @cortinico
    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)

  2. github-actions commented on Dec 8, 2022

    @github-actions

    👋 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.

  3. added
    StaleIssues/PR that are not getting much activity and are closer to be closed
    on Dec 8, 2022
  4. cortinico commented on Dec 8, 2022

    @cortinico
    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

  5. removed
    StaleIssues/PR that are not getting much activity and are closer to be closed
    on Dec 8, 2022
  6. github-actions commented on Mar 9, 2023

    @github-actions

    👋 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.

  7. added
    StaleIssues/PR that are not getting much activity and are closer to be closed
    on Mar 9, 2023
  8. cortinico commented on Mar 9, 2023

    @cortinico
    Contributor

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

  9. removed
    StaleIssues/PR that are not getting much activity and are closer to be closed
    on Mar 9, 2023
  10. github-actions commented on Jun 8, 2023

    @github-actions
  11. added
    StaleIssues/PR that are not getting much activity and are closer to be closed
    on Jun 8, 2023
  12. added
    Never gets stalePrevent issues/PRs from getting stale
    and removed
    StaleIssues/PR that are not getting much activity and are closer to be closed
    on Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Never gets stalePrevent issues/PRs from getting stale

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions