Fix codegen for projects in hidden folders

[dinisnunes1]

Summary:

Fixes #55243

Fixes an issue where iOS codegen fails when the React Native project is located inside a hidden folder (a folder starting with ., such as ~/.jenkins/workspace/ or /.buildkite/builds/).

The issue was reported for React Native 0.79.4, but the bug affects all subsequent versions including the current main branch.

The findFilesWithExtension function was checking if the entire absolute path contained /. to skip hidden folders. This caused false positives when the project workspace itself was under a hidden folder, resulting in all files being incorrectly filtered out and codegen producing empty results.

The fix changes the check to only look at the current filename being iterated (file.startsWith('.')) rather than the full path, while preserving the existing .pnpm exception.

Changelog:

[iOS] [Fixed] - Fix codegen failing when project is inside a hidden folder

Test Plan:

Added unit tests for findFilesWithExtension that verify:

• Hidden files/folders are still correctly skipped
• The .pnpm folder exception still works
• Projects under hidden folders (e.g., /.jenkins/workspace/) now work correctly

Run tests with:

yarn jest packages/react-native/scripts/codegen/__tests__/generate-artifacts-executor-test.js --testNamePattern="findFilesWithExtension"

All 3 tests pass. The critical test works when project is under a hidden folder fails without the fix (returns empty array) and passes with the fix.

Example of the codegen failing on a dotted path 🔴

• pod install logs on Github Actions
• example based on the Reproducer repo

Example of the codegen crawling working on a dotted path - with the fix ✅

• pod install logs on Github Actions
• example based on the Reproducer repo - branch with RN 0.83.1 patched

[meta-cla]

Hi @dinisnunes1!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[meta-codesync]

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

[react-native-bot]

This pull request was successfully merged by @dinisnunes1 in a12b442

^{When will my fix make it into a release? | How to file a pick request?}

[meta-codesync]

@cortinico merged this pull request in a12b442.

[react-native-bot]

This pull request was successfully merged by @dinisnunes1 in 4733593

^{When will my fix make it into a release? | How to file a pick request?}