Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upUse yarn instead of npm #46
Merged
+5
−5
Conversation
Since you already have a yarn.lock, it seems to make sense to encourage devs to use exactly the same deps. And while we are at it, why not use yarn consistently for everything?
|
Hi! I agree, thanks for the patch |
|
Can't wait to have sync in brave :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
domoritz commentedJan 22, 2017
Since you already have a yarn.lock, it seems to make sense to encourage devs to use exactly the same deps. And while we are at it, why not use yarn consistently for everything?