chore: 🚜 use npm client when publishing #72
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
... This is quite annoying but the publish with yarn fails because it tries to prompt the user event if lerna provides a version. Not clear how to solve this in travis env. Found this issue yarnpkg/yarn#2591 and it seems to be an issue with the environment. Whaterver the case using npm should fix the problem. I hope
Fetz
approved these changes
Aug 3, 2018
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
... This is quite annoying but the publish with yarn fails because it
tries to prompt the user event if lerna provides a version. Not clear
how to solve this in travis env. Found this issue
yarnpkg/yarn#2591 and it seems to be an issue
with the environment. Whaterver the case using npm should fix the
problem. I hope