`react-native-git-upgrade` uses npm inside yarn workspaces

[mike-marcacci]

• Review the documentation: https://facebook.github.io/react-native
• Search for existing issues: https://github.com/facebook/react-native/issues
• Use the latest React Native release: https://github.com/facebook/react-native/releases

Description

react-native-git-upgrade fails to detect usage of yarn when the react-native app root is a yarn workspace. Currently is looks for yarn.lock in the package root which won't exist if it's in a workspace.

Obviously, since NPM doesn't support workspaces, it's extra important that yarn is used in these situations.

However, I'm not exactly sure what the best strategy is here... should we simply walk up the tree until we find a yarn.lock file? Does yarn itself export a utility to detect workspaces?

[react-native-bot]

We are automatically closing this issue because it does not appear to follow any of the provided issue templates.

Please make use of the bug report template to let us know about a reproducible bug or regression in the core React Native library.

If you'd like to propose a change or discuss a feature request, there is a repository dedicated to Discussions and Proposals you may use for this purpose.