Files
orbit/apps/cli/pkg.config.json
Gabriel Donadel Dall'Agnol 9cfc51e589 [cli][menu-bar] Put the Hermes CLI behind ORBIT_HERMES_CLI (off by default)
Without the flag the app builds exactly as before: React Native's stock Hermes,
React Native's own JSI and the pkg-built CLI binaries (Release builds only),
so main's Podfile.lock, pkg config, entitlements, EAS and e2e workflows are
unchanged.

pod install with ORBIT_HERMES_CLI=1 (or "hermesCli": "true" in
Podfile.properties.json) opts into Hermes V1 from hermes-node's pin, its JSI,
and the orbit-cli launcher + orbit-cli.hbc in every configuration (yarn
archive:hermes / codesign:hermes). pod install records the choice in
Pods/.orbit-hermes-cli for the build phases, and without the flag puts React
Native's JSI back.

The app bundles the CLI as Contents/Resources/cli/ either way and runs
cli/orbit-cli when present, otherwise the pkg binary for the architecture.
2026-11-14 16:18:03 -08:00

15 lines
434 B
JSON

{
"pkg": {
"assets": [
"../../node_modules/macos-export-certificate-and-key/**/*.node",
"../../node_modules/ipa-resign/node_modules/macos-export-certificate-and-key/**/*.node",
"../../node_modules/ipa-resign/bin/anisette",
"../../node_modules/ipa-resign/bin/zsign"
],
"scripts": [
"../../node_modules/fflate/lib/*.cjs"
],
"targets": ["node18-macos-arm64", "node18-macos-x64"]
}
}