-
Notifications
You must be signed in to change notification settings - Fork 24.8k
update base64-js version. follow up #6961 #6937
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
By analyzing the blame information on this pull request, we identified @lindskogen, @cpojer and @sahrens to be potential reviewers. |
@mkonicek Can you check on this since you guys update the internal fb npm cache manually. |
I don't see why that's the case. |
@@ -138,7 +138,7 @@ | |||
"babel-register": "^6.6.0", | |||
"babel-types": "^6.6.4", | |||
"babylon": "^6.6.4", | |||
"base64-js": "^0.0.8", | |||
"base64-js": "^1.0.4", |
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.
Why not ^1.1.0
as that version seems to have a bunch of improvements over 1.0.4
(whereas 1.1.1
and 1.1.2
seem to only be about aesthetics).
Pro-tip: make sure you explain the motivation for your PR. You're currently not giving any, instead pointing to other PRs which also don't give motivation. If you want to make it easier for reviewers, and quicker for you, I suggest editing your PR note to include a small note about why you want this change. Also please don't forget a test plan. |
@zxcpoiu updated the pull request. |
@philikon why this PR exist and described as a follow up of #6961 are because:
This PR should be closed if no one needed
If no one thinks this is necessary, then this PR should be closed. thanks again for all the great jobs. |
I can't recall why this was upgrade was needed. Since @philikon is handling things in the other PRs, this one should definitely be closed. |
Upgrading sounds good. I'll need to merge this manually into our internal node_modules store though. |
@cpojer would you mind taking a look at this pull request? It's been a while since the last commit was reviewed. |
This is a follow up of PR facebook#6327 by @dewe and @jeremyong as @mkonicek indicated this should split into a separate PR
@facebook-github-bot import |
Thanks for importing. |
It's been a while since the last commit was reviewed and the labels show this pull request needs review. Based on the blame information for the files in this pull request we identified @cpojer as a potential reviewer. Could you take a look please or cc someone with more context? |
Took a while to get back to this one :) @facebook-github-bot import |
Thanks for importing. If you are an FB employee go to Phabricator to review internal test results. |
Motivation
This is originally a follow up of PR #6327 by @dewe and @jeremyong
And @mkonicek indicated this should split into a separate PR.
Now @philikon takes over #6327 as #6961
Test Plan:
According to #6961 and #6889
Load WebSocketExample in UIExplorer app and start websocket test server script and test sending binary data on both iOS and Android