-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Replace npm shrinkwrap with yarn.lock #1278
Conversation
Do we need to adjust travis? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we could include yarn into our CI as soon as we publish artifacts. Looks good!
I suppose we could use yarn within travis to install the deps. Thinking about it, we probably should do that since we no longer use shrinkwrap (which means EDIT: just saw your comment above. Yeah, once we build artifacts using yarn in CI becomes essential. Right now it's just a nice-to-have if we're not really building artifacts. |
This requires a bit more testing. After deleting |
Yarn Cheatsheet: https://duckduckgo.com/?q=yarn+cheatsheet&ia=cheatsheet&iax=1 |
Yay, starting from today travis natively supports yarn: travis-ci/travis-build#895 |
@hiddentao I fixed the 7zip OS-specific download by adding them as optionalDependencies to the package.json as described in https://yarnpkg.com/en/docs/dependency-types#toc-optionaldependencies. Eventually updating yarn also does the trick as it now internal adds them. |
This PR is ready to be merged. It includes:
|
LGTM 👍 |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Did a fresh install using yarn and it took <1min. Way faster than npm install.
This replaces shrinkwrap with yarn.lock file so that we'll have more deterministic builds.
Info on yarn -> https://yarnpkg.com/