-
Notifications
You must be signed in to change notification settings - Fork 20
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
Land Yarn #169
Conversation
d1b6db3
to
0f95a2f
Compare
Yarn 0.16 has been released, testing build infrastructure. |
585ce2e
to
37d4946
Compare
71c60bf
to
32d8759
Compare
Urgh, and now More specifically |
This was supposedly fixed with yarnpkg/yarn#1739, but this still fails as of Yarn 0.17.0. |
be62259
to
fc990ec
Compare
@beheh where are we at on this? Is it still blocked on yarn? |
It looks like the |
Yep, looks fine. I'm personally not feeling to good right now, but I'll try and land this soon. |
|
b995d6b
to
2e9aace
Compare
325c164
to
47db62e
Compare
Finally looking good with yarnpkg/yarn#2537, included in yarn 0.20.0. |
Yarn is a new package manager from Facebook and Google: https://yarnpkg.com/. It's been more reliable and much faster on my development machine, and I hope to speed up build time like this, since dependency installation is a non-trivial amount of time spent every single time.
The only caveat is that Travis currently always will run. We can override this behaviour.npm install
when it detects a package.json and I'd like a way to disable this: travis-ci/travis-ci#6713 (I've submitted a PR)We'll also have to install yarn to our internal build server, but that should be pretty straight forward.