React Native isn't compatible with yarn pnp

Environment

[skip envinfo] react-native info doesn’t work in this scenario: Command ``info`` unrecognized. Make sure that you have run ``npm install`` and that you are inside a react-native project.

Description

If you enable yarn pnp for a React Native app, it doesn’t work. Perhaps something is hardcoded to look in ./node_modules?

The resulting error is: Error: Couldn't find a suitable Node resolution for unqualified path "<path-to-your-rn-project>/node_modules/react-native/local-cli/cli.js"

Reproducible Demo

• Create a new react native app via react-native init someproject
• cd someproject
• enable yarn pnp: yarn --enable-pnp
• yarn start

[bartolkaruza]

That path is hard coded in the project.pbxproj file of the iOS app. That’s just one spot though, the native app projects resolve the native module dependencies using file paths pointing to node_modules. They are unable to run a JS based resolver to find those dependencies in the current conventions of React Native. This looks like a tough nut to crack, considering the PNP proposal only seems to talk about node.js and modifying the require hook. Any modifications to RN that only accounts for PNP would mean that npm won’t work with React Native anymore. Maybe you can open a discussion for this in the discussions repo? I doubt this will be resolved quickly as an issue.

[empyrical]

I am tackling this issue first over at the repo for react-native-cli:

https://github.com/react-native-community/react-native-cli/issues/27

I think the bulk of the work for this is in the CLI half of React Native