fix(cli): resolve react-native script subpaths through the exports map

[chrfalch]

Summary:

Two CLI commands are broken on main right now. Both fail the moment you run them:

$ npx react-native spm add
error Cannot find module '.../node_modules/react-native/scripts/setup-apple-spm'

$ npx react-native codegen
error Cannot find module '.../node_modules/react-native/scripts/codegen/generate-artifacts-executor'

What happened. #57652 moved these two command wrappers into community-cli-plugin. Each one loads a helper script out of the react-native package by name:

require.resolve('react-native/scripts/setup-apple-spm');

Anything starting with react-native/ is looked up through the exports list in that package's package.json. This lookup is strict — it takes the path exactly as written. It will not add a missing .js, and it will not find the index.js inside a folder. Node's older lookup style did both of those automatically, and both wrappers were relying on it:

what the wrapper asked for	what's actually there	needed
scripts/setup-apple-spm	a file named setup-apple-spm.js	.js on the end
scripts/codegen/generate-artifacts-executor	a folder containing index.js	/index.js on the end

The fix. Write both paths out in full. That's a one-line change in each wrapper; nothing else about the commands changes.

This was found by the new SwiftPM iOS CI job in #57659, where every build failed on the spm command.

Changelog:

[GENERAL] [FIXED] - Fix react-native spm and react-native codegen failing with "Cannot find module"

Test Plan:

Added packages/community-cli-plugin/src/commands/__tests__/reactNativeSubpathResolution-test.js. It reads the command wrapper files, picks out every react-native/... path they reference, and checks each one can actually be loaded. That covers both commands today and any wrapper added later.

Why the test runs node in a subprocess: Jest redirects react-native to the source folder, which skips the exports list altogether. A test that does the lookup inside Jest therefore passes even while the real command is broken — I wrote that version first and it went green against the broken code. Running a separate node process is what makes the test meaningful.

Test fails before the fix, passes after:

# before
✕ codegen.js resolves react-native/scripts/codegen/generate-artifacts-executor
✕ spm.js resolves react-native/scripts/setup-apple-spm
Tests: 2 failed, 1 passed, 3 total

# after
✓ codegen.js resolves react-native/scripts/codegen/generate-artifacts-executor/index.js
✓ spm.js resolves react-native/scripts/setup-apple-spm.js
Tests: 3 passed, 3 total

Same result checking the paths directly, outside Jest:

node -e "require.resolve('react-native/scripts/setup-apple-spm')"                                # fails
node -e "require.resolve('react-native/scripts/setup-apple-spm.js')"                             # works
node -e "require.resolve('react-native/scripts/codegen/generate-artifacts-executor')"            # fails
node -e "require.resolve('react-native/scripts/codegen/generate-artifacts-executor/index.js')"   # works

flow focus-check, ESLint and Prettier are clean on the changed files.

[chrfalch]

Verified end-to-end on a clean main worktree (54656471a54) — both commands fail today, and the two-line change repairs both.

Before (main, unmodified):

$ npx react-native spm download --artifacts /tmp/probe      # from private/helloworld/ios
error Cannot find module '.../node_modules/react-native/scripts/setup-apple-spm'
    at Object.func (.../packages/community-cli-plugin/src/commands/spm.js:109:35)
exit 1

$ npx react-native codegen --path . --platform ios --outputPath /tmp/out   # from private/helloworld
error Cannot find module '.../node_modules/react-native/scripts/codegen/generate-artifacts-executor'
    at Object.func (.../packages/community-cli-plugin/src/commands/codegen.js:49:47)
exit 1

After (same worktree, only the two specifier lines changed):

$ npx react-native spm download --artifacts /tmp/probe
[setup-apple-spm] Running SPM download in: .../private/helloworld/ios
[setup-apple-spm] React Native version: 1000.0.0
[download-spm-artifacts] Resolved nightly: 0.88.0-nightly-20260728-...
[download-spm-artifacts] Fetching snapshot metadata: https://central.sonatype.com/...

Gets past module loading into real artifact downloading (I stopped it with a 180s timeout rather than waiting for the full fetch).

$ npx react-native codegen --path . --platform ios --outputPath /tmp/out
exit 0

Runs to completion, writing real artifacts (RCTThirdPartyComponentsProvider, RCTModuleProviders, ReactAppDependencyProvider, Package.swift).

No Cannot find module in either command's output afterwards.

Worth noting npx react-native codegen has no CI coverage at all — no workflow invokes it, and Jest's moduleNameMapper bypasses the exports lookup — so nothing currently in the pipeline would catch this.

[meta-codesync]

@fabriziocucci has imported this pull request. If you are a Meta employee, you can view this in D113895593.

[fabriziocucci]

Superseded by #57718.