fix: support more extensions when looking for react-native.config.*

[tido64]

Description

Support more extensions when looking for react-native.config.*

See also #2429

Platforms affected

• Android
• iOS
• macOS
• visionOS
• Windows

Test plan

n/a

[tido64]

cc @szymonrybczak

[szymonrybczak]

😮 Really interesting!

The thing is that if someone will call configureProjects function not directly in react-native.config.* file but through some helper in other file the value inside stacktrace will be wrong, but there's always fallback to default search.

[tido64]

The thing is that if someone will call configureProjects function not directly in react-native.config.* file but through some helper in other file the value inside stacktrace will be wrong, but there's always fallback to default search.

Hmm... we should probably allow passing in the project root to avoid searching altogether. If we search the whole stack, we could end up in weird places outside the project. None of the alternatives are robust.

[szymonrybczak]

@tido64 you can also leverage root property from react-native config command which is based on nearest package.json IIRC

[tido64]

@tido64 you can also leverage root property from react-native config command which is based on nearest package.json IIRC

I believe that would cause a loop. react-native config reads a react-native.config.js that calls configureProject() which calls react-native config.