Preload Yarn PnP and add autolinking fallback in Podfile

[hyochan]

Changelog:

[iOS] [Fixed] - Fix autolinking under Yarn PnP in the HelloWorld Podfile.

Summary

Make the HelloWorld iOS Podfile robust under Yarn 3 Plug’n’Play by preloading PnP and adding a safe fallback.

Test Plan

• PnP: init new app → set Yarn Berry + nodeLinker pnp → yarn install → npx pod-install → codegen runs, Pods generated, no "react_native_pods.rb" error, iOS build OK.
• Non-PnP: init new app → yarn install (or npm i) → npx pod-install → behavior unchanged.

[hyochan]

Because Danger CI kept failing on the changelog format (even though it was written correctly), I decided to keep the PR description short for now.
Below, I’ve re-included the original detailed explanation and screenshots as an addendum for reviewers’ reference.

Preload Yarn PnP runtime and add a safe fallback for use_native_modules! to make the iOS template resilient under non-standard setups (e.g., Yarn 3 PnP).

• Preload .pnp.cjs via NODE_OPTIONS during pod install so Node can resolve React Native CLI scripts when CocoaPods spawns Node without Yarn PnP hooks.
• Wrap use_native_modules! with a fallback that derives reactNativePath from require.resolve('react-native/package.json') when CLI config lookup fails.
• Execute config.sh with bash (not sh) to match the script’s shebang and ensure compatibility on macOS/CI.

Motivation: CocoaPods invokes Node without Yarn PnP hooks, which leads to failures such as:

• Cannot find module 'react-native/scripts/react_native_pods.rb'
• Autolinking terminating early with advice to install @react-native-community/cli

This change is a no-op for non-PnP projects and preserves default behavior when CLI config resolution succeeds.

---

Test Plan

PnP project (Yarn 3, Plug’n’Play)

npx @react-native-community/cli@latest init AwesomeProject
cd AwesomeProject
corepack enable (if needed)
yarn set version berry (if not already on Yarn 3)
yarn config set nodeLinker pnp
yarn install
npx pod-install

Validate:

• ✅ Codegen runs
• ✅ Pods project is generated successfully
• ✅ No “Cannot find module …/react_native_pods.rb”
• ✅ iOS build succeeds (ios/AwesomeProject.xcworkspace)

---

Non-PnP project (classic node_modules)

npx @react-native-community/cli@latest init AwesomeProject
cd AwesomeProject
yarn install   # or npm i
npx pod-install

Validate:

• ✅ Behavior unchanged from today
• ✅ Template continues to work as before

---

Additional checks from this repo’s HelloWorld

• ruby -c private/helloworld/ios/Podfile → syntax OK

• bundle exec pod install in private/helloworld/ios:

  • Preflight runs; on failure, it cleanly falls back to minimal config (no autolinking) without exiting.
  • RN codegen artifacts (ReactCodegen, ReactAppDependencyProvider) are generated.

---

Behavioral Guarantees

• Gated by presence of .pnp.cjs → no-op on non-PnP setups.
• When CLI config works, the fallback is not used.
• When CLI config fails, fallback via require.resolve('react-native/package.json') unblocks autolinking/Pods.

---

Screenshots

Without this patch

With this patch

[hyochan]

https://github.com/facebook/react-native/actions/runs/17631368517/job/50099276962?pr=53723 The failure doesn't seem to be related to current PR!

[react-native-bot]

This PR is stale because it has been open for 180 days with no activity. It will be closed in 7 days unless you comment on it or remove the "Stale" label.

[react-native-bot]

This PR is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.