Skip to content
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 vs npm #319

Closed
ryannealmes opened this issue Nov 15, 2016 · 3 comments
Closed

yarn vs npm #319

ryannealmes opened this issue Nov 15, 2016 · 3 comments

Comments

@ryannealmes
Copy link
Contributor

ryannealmes commented Nov 15, 2016

I see you guys have added yarn to the repo. Is yarn not an npm replacement? npm install is still used to setup the project not yarn.

Is there a reason for this? Just trying to learn/understand why it's being used. My own reading hasn't given enough information to come to my own conclusion.

Thanks.

@nickytonline
Copy link
Collaborator

nickytonline commented Nov 15, 2016

@ryannealmes, yarn is the way going forward, but you're not forced into using it at the moment. You can use npm or yarn if you're using this project.

The only time you need to use yarn right now is if you contribute to the project and add/remove/update a package because the yarn.lock file needs to be updated and our CI uses yarn.

We should probably updated the docs to say you can install via yarn or npm.

@ryannealmes
Copy link
Contributor Author

Great thanks! That answers my question.

@coryhouse
Copy link
Owner

Good question @ryannealmes. I left it out of docs since it's totally optional and will stay that way. I figure anyone who has questions about what Yarn is doesn't need it. It's just a nice convenience/time saver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants