Tommy Nguyen

@huntie: Yes, I think adding a new field like you described makes the most sense. It would allow for future expansions. If we're all agreeing on this approach, what would...

cc @brentvatne in case you have better ideas or feedback on this.

Another interesting bit I discovered today: Even with `codegenConfig` present, it's not a guarantee that the library supports New Arch + autolinking. I've spent days (on separate occasions) trying to...

> Is this the preferred approach then? nit: `react-native-config` vs `codegenConfig` are mixing camel case with kebab case, not great. > > ``` > "react-native-config": { > "metro-exports-mode": "strict", >...

@mikehardy: Should we close this? Prefabs will be enabled as of 0.71 so I don't know how relevant this will be for 99% of use cases.

What does your `tsconfig.json` look like? Does it match with how you've configured `module-resolver`?

Am I understanding you correctly if I say you have a structure that looks something like: ``` root ├── app1 │ ├── │ └── package.json ├── app2 │ ├── │...

As far as I can tell, each root folder is treated as a project. If a folder contains a `tsconfig.json`, it is treated as a TS project and its files...

Use shared configs: https://www.typescriptlang.org/tsconfig#extends

I think it makes sense to add it. My only concern is that we should _not_ make the `react` capability take a dependency on it. It's not a given that...