-
Notifications
You must be signed in to change notification settings - Fork 24.7k
Added e2e tests for npm@2 and npm@3 #6364
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
Conversation
Considering that community runs both we need to make sure that react native can be published and installed with both
@frantic now the exit codes and stderr is ok? |
By analyzing the blame information on this pull request, we identified @mkonicek, @bestander and @frantic to be potential reviewers. |
@mkonicek this is what you had in mind?
But I did not want to make e2e-test script more complex and maybe it will be an overkill |
…hes don't work in travis anyway
@bestander updated the pull request. |
@@ -2,11 +2,6 @@ language: objective-c | |||
|
|||
osx_image: xcode7.2 | |||
|
|||
cache: |
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 tested this setting does not do anything, .nvm is empty on every build and npm install is done fresh.
Not too bad, npm is stable recentlly and takes just 3 minutes
👍 |
@facebook-github-bot shipit |
Thanks for importing. If you are an FB employee go to Phabricator to review. |
Need to make sure we can use both versions of npm client for publishing and installing
Test plan (required)
Make sure tests pass on both Travis and Circle CI.