-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metro-bundler-config-yarn-workspaces: ambiguous resolution of react-native #16
Comments
This issue was fixed by simply following the instructions regarding For anybody who stumbles on this issue, and is using a vanilla React Native config without Expo, the steps you need to follow start with Thanks for making these helpful instructions, and sorry for the issue spam! Closing now. |
@Ashoat do you have an example of this package with vanilla react native project without expo? |
My SquadCal repo is a working example of yarn workspaces with a React Native project. I also have my custom version of |
how do you run from root or inside |
From the |
I am trying to use yarn workspaces together with React Native. Previously, I was using
[email protected]
,[email protected]
, and[email protected]
, and everything was working fine out-of-the-box. I didn't need a customrn-cli.config.js
.After upgrading to
[email protected]
and[email protected]
, things are no longer working cleanly. The list of watched directories that Metro prints when it starts up no longer includes the root folder of the monorepo, and as such attempts to resolve "secondary" dependencies (ie. dependencies of dependencies, which yarn workspaces store in the root folder) fail.I'm trying to use the
metro-bundler-config-yarn-workspaces
package to rectify the situation. However, I'm getting an ambiguous resolution error when I try to use it:Perhaps the blacklist is misconfigured? Would appreciate any help I could get. If you'd like more details, the issue I posted on the metro repo has them.
The text was updated successfully, but these errors were encountered: