-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Yarn installation error on create-nx-workspace
and Expo setup due to peer dependencies are incorrectly met
#26257
Comments
create-nx-workspace
and Expo setup error due to peer dependencies are incorrectly met
create-nx-workspace
and Expo setup due to peer dependencies are incorrectly met
create-nx-workspace
and Expo setup due to peer dependencies are incorrectly met
create-nx-workspace
and Expo setup due to peer dependencies are incorrectly met
create-nx-workspace
and Expo setup due to peer dependencies are incorrectly met
create-nx-workspace
and Expo setup due to peer dependencies are incorrectly met
in Yarn
create-nx-workspace
and Expo setup due to peer dependencies are incorrectly met
in Yarncreate-nx-workspace
and Expo setup due to peer dependencies are incorrectly met
I've just upgraded the following 2 packages with these versions: After doing this, I was able to install other packages again. @guillempuche maybe this will work for you too (as a temporary solution) |
Thanks for offering a solution, @JeremiahKoeiman. Let's see if the Nx team fixes it. |
i think there are 2 packages with dependency errors:
it should be fixed in nx 19.2.0 |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
I could be because of Yarn's
node-linker
as PnP.Creating the repo with
npm
works fine.Expected Behavior
Create a monorepo with Expo app.
GitHub Repo
No response
Steps to Reproduce
npx create-nx-workspace test-nx-expo --name=text-expo --pm yarn
Nx Report
Failure Logs
Package Manager Version
yarn 4.1.1
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: