[chrfalch]

Summary:

In the SwiftPM pipeline, every sync reads the podspec of each npm dependency to collect its HEADER_SEARCH_PATHS. (That can even start a pod ipc spec process for each dependency), and the result is never used.

This change removes the read and the code that carried its result:

• extractPodspecHeaderSearchPaths and its call in autolinkingDepToSpmTarget (generate-spm-autolinking.js)
• the headerSearchPaths field on SpmTarget and SynthPackageSpec (spm-types.js)
• the root/ prefix step in main() and the .headerSearchPath(...) output in generateSynthPackageSwift

The podspec reader (read-podspec.js) and the scaffolder (scaffold-package-swift.js) still use header search paths. They do not change.

This PR does not depend on other open PRs.

Changelog:

[INTERNAL] [REMOVED] - Stop reading unused podspec header search paths during SwiftPM sync

Test Plan:

• New test in generate-spm-autolinking-test.js: an npm dependency whose podspec sets HEADER_SEARCH_PATHS must not cause a call to the podspec reader. Before the change it failed with Expected number of calls: 0, Received number of calls: 1. After the change it passes.
• node_modules/.bin/jest --no-cache -i packages/react-native/scripts/spm: 23 of 23 suites and 1129 of 1129 tests pass.
• Generated output for RNTester, before and after, with node packages/react-native/scripts/spm/generate-spm-autolinking.js --app-root packages/rn-tester --react-native-root packages/react-native --autolinking-json <file> --output <dir>:
  • With RNTester's npm dependencies, both runs stop with the same missing-manifest error and write no files.
  • With only RNTester's app-local modules, both runs write the same 7 Package.swift files. diff -r finds no differences.
• ESLint and Prettier pass on the changed files. Flow finds no errors in them. I did not run a full yarn flow-check, because it fails locally on unrelated vendored files.

[cipolleschi]

Thanks @chrfalch, this looks good to me.

I checked main() to make sure the field really was dead. Every npm dependency that goes through autolinkingDepToSpmTarget either has its own Package.swift, so the generated-manifest step is skipped, or ends up in missingManifests, which throws before any manifest is written. The only targets that still get a generated manifest are app-local spm.modules. Those never had headerSearchPaths set and don't read podspecs. So this removes a podspec read (and possibly a pod ipc spec process) per dependency on every sync, with no change to the output.

The case the old comment cared about (<react/renderer/components/safeareacontext/...> includes) is still covered: scaffold-package-swift.js writes the podspec's header search paths into the Package.swift it scaffolds.

I left one small inline nit; it's not blocking.

[meta-codesync]

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