expo-brownfield

原文涵盖的主题

• Expo Brownfield
• Inspect the host first
• Pick an approach
• References
• Shared prerequisites
• Select compatible versions
• Verify the feature in the host
• Submitting Feedback

A brownfield app is an existing native iOS or Android app that adopts React Native incrementally, as opposed to a greenfield app that is React Native from day one. Identify the existing app entry point, navigation owner, native build system, deployment targets, and any React Native runtime already linked. Record the installed Expo, React Native, and brownfield package versions from the lockfile. Adding EAS Build or Submit to a Swift app alone does not require React Native; route that task to eas-app-stores. Preserve the host's SwiftUI App / UIKit window and native screens when embedding a feature. Do not run prebuild in a manually maintained native host, including during troubleshooting. An isolated Expo producer may use CNG; keep its generated ios/ and android/ separate from the consuming app. Expo supports two distinct ways to add React Native to a brownfield project: | Approach | What ships to the native app | When to choose | | -------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | Isolated | Prebuilt AAR / XCFramework | Native team doesn't need Node or RN toolin

这里只展示节选，请以完整原文和当前要求为准。