-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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 + Create React App Umbrella #1189
Comments
This is tracked in yarnpkg/yarn#2161. |
This issue I posted might be related: I was excited to start using it with my Meteor projects, but went back to npm as I don't find yarn to be all that reliable. |
Also interesting: apparently installed size is larger with Yarn? https://twitter.com/petrhurtak/status/812356423795568640 |
Apparently the disk size issue is very bad. |
The disk size issue might be related to yarnpkg/yarn#2306. It'd be worth opening an issue on the Yarn GitHub project to track it. |
Another issue report related to binaries: #1370. |
-snip- yarnpkg/yarn#2649 |
@Timer Mind filing a Yarn bug? |
Filed. 😄 |
Unmet peer dependency warning (yarnpkg/yarn#2132) has been fixed in Yarn 0.22.0. |
With regard to "issues with flaky connections" I've added the following comment on yarnpkg/yarn#746 OK I had the same issues when building create-react-app inside docker, never managed to install. Backed out one step to the vagrant box, running on VirtualBox, installed node yarn etc and then again ran create-react-app. Same issue but it did get further, downloaded more packages, than under docker. Changed the network settings on vagrant from NAT to Bridged: Old: New: You can switch back the configs once you have successfully done what you needed to. Ran create-react-app again and it looked like it it would complete, despite the odd "warning There appears to be trouble with your network connection. Retrying..." Nope failed on ESOCKETTIMEDOUT, but just about there! Ran it again, success! Back to docker version, long story short it eventually successfully built. Good job I'm doing intermediate builds... Networks can be flaky, some more than others. I would like to see the following be able to be set in yarn config: download_max_retry - does what it says on the tin and defaults to 20 Hope this helps and thanks for the tools! |
Seems like this is as good as it gets for now. |
We shipped Yarn integration but there are a few small annoyances.
I'd like to consolidate them.
When they are fixed I'll feel comfortable recommending Yarn to CRA users more broadly.
yarn@0.18
was released withlatest
tag for some time since it started failing our CI (Fix end-to-end test on Yarn #1167). I'm happy to help test Yarn by opting into usingnext
builds on CI, but I want to make sure we have a process in place that Yarn RC releases don't becomelatest
until they're well tested.peerDependencies
warning has a false positive Unmet peer dependency warning when the peer dependency is installed at the same time yarnpkg/yarn#2132fsevents
) Error in jest watch when using yarn for dependency installation #1474, Question: react-scripts start constantly @ 30% CPU #1670yarn global add
doesn't work on Windows When installing global modules, Yarn tries to create .cmd file in wrong directory yarnpkg/yarn#2192yarn global add
doesn't work with nvm "yarn global add" doesn't globally install packages if .yarn-cache was restored yarnpkg/yarn#1151 (comment)The text was updated successfully, but these errors were encountered: