Remove Hermes vendoring once React Native ships a Hermes with Node-API

首先检查 React Native 的 version.properties，并检查 API/napi/ 对应的 Hermes tag，然后验证随附的 Android 和 Apple 工件是否暴露所需的 Node-API 符号和头文件。在移除 vendoring 路径之前，检查列出的 CLI、Gradle、C++、podspec、workflow、app、文档和 package 文件。测试应用能够在不使用 REACT_NATIVE_OVERRIDE_HERMES_DIR 或 build-from-source 配置的情况下，基于原生 React Native 构建并通过测试，即表示完成。

Tracking the removal of vendor-hermes and everything that hangs off it, gated on React Native shipping a Hermes that carries Node-API.

Why we vendor today

After #372 we no longer patch Hermes — we build it from a pinned commit on the static_h branch, which carries the first-party Node-API implementation under API/napi (target hermesNapi). The pin lives in packages/host/src/node/cli/hermes.ts, and the host calls into it directly (hermes_napi_create_env in packages/host/cpp/CxxNodeApiHostModule.cpp, with the hermes_napi_host struct mirrored in packages/host/cpp/HermesNapiHost.hpp).

React Native's own Hermes doesn't have that code yet, which is the only reason we need REACT_NATIVE_OVERRIDE_HERMES_DIR — and therefore the only reason consumers have to build React Native from source at all.

The gate

React Native doesn't tag every nightly, so read the head of the default branch rather than a release:

1. packages/react-native/sdks/hermes-engine/version.properties on the default branch of facebook/react-native → HERMES_VERSION_NAME.
2. Check whether facebook/hermes at tag hermes-v$HERMES_VERSION_NAME has an API/napi/ directory.

State as of 2026-09-19:

• HERMES_VERSION_NAME=260318099.0.2 (unchanged since at least 2026-09-14 — five consecutive checks, 2026-09-14 through 2026-09-19, have all read the same value)
• API/napi/hermes_napi.h → still 404 at hermes-v260318099.0.2, while API/hermes/hermes.h resolves at the same tag — so the tag is valid and still carries no Node-API. No open PR references this issue. Still nothing to poll for besides re-checking the gate.

That's the cheap signal to poll. Something like:

version=$(curl -fsSL https://raw.githubusercontent.com/facebook/react-native/main/packages/react-native/sdks/hermes-engine/version.properties | sed -n 's/^HERMES_VERSION_NAME=//p')
curl -fsSLo /dev/null "https://raw.githubusercontent.com/facebook/hermes/hermes-v$version/API/napi/hermes_napi.h" && echo "Node-API has landed in RN's Hermes ($version)"

Necessary, but not sufficient

The version check tells us the source has Node-API in it; before dropping anything we still need the shipped artifacts to expose it:

• the hermes-engine AAR's libhermesvm.so must export hermes_napi_create_env (Hermes has to build the hermesNapi target and keep it visible under its global -fvisibility=hidden, cf. facebook/hermes#2106 — see the pin comment in hermes.ts),
• the same for the Hermes framework shipped through the podspec on Apple platforms,
• hermes_napi.h (or an equivalent public header) needs to reach us through prefab / the framework headers, so HermesNapiHost.hpp can include it instead of mirroring the struct,
• IHermes::getVMRuntimeUnsafe() still has to be reachable from the JSI runtime.

The real acceptance test is the test app building and passing against a stock React Native with no REACT_NATIVE_OVERRIDE_HERMES_DIR set and no build-from-source configuration.

What removal touches

• packages/host/src/node/cli/hermes.ts — the vendor-hermes command, plus its registration in packages/host/src/node/cli/program.ts (a breaking CLI change, so it wants a major changeset)
• packages/host/android/build.gradle:7-17 — the REACT_NATIVE_OVERRIDE_HERMES_DIR guard, and packages/host/src/node/gradle.test.ts, which asserts that error
• packages/host/scripts/patch-hermes.rb and its require_relative in the podspec
• .github/workflows/check.yml:330-333 — the vendoring step in the Android job
• apps/test-app/android/gradle.properties — react.buildFromSource=true becomes unnecessary
• packages/host/cpp/HermesNapiHost.hpp — include the real hermes_napi.h instead of mirroring hermes_napi_host, which also removes the "re-diff on every pin bump" hazard
• docs/ANDROID.md — most of it disappears; Android stops needing a source build (see #411 for its current state)
• README.md (the supported-versions note), packages/host/README.md, AGENTS.md § Critical Build Dependencies
• packages/host/package.json — the react-native peer dependency can widen from a single nightly to a real range

Related

• #177 — prebuilt Node-API Hermes, the interim mitigation if this takes a while
• #392 — react-native-macos blocked on the same story
• #188 — the consumer-side Gradle settings helper, which becomes moot along with the source-build requirement