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

Fix Travis browser tests dependency #2898

Merged
merged 2 commits into from
Jul 26, 2017
Merged

Fix Travis browser tests dependency #2898

merged 2 commits into from
Jul 26, 2017

Conversation

ScottFreeCode
Copy link
Contributor

@ScottFreeCode ScottFreeCode commented Jun 21, 2017

Does NOT fix the Sauce 20,000ms disconnect issue.

Does fix the newer issues that appeared just this past day.

This fixes Travis browser tests (except for the Sauce 20,000ms disconnect issue), #2897 fixes AppVeyor Node 0.10 tests; put them both in master and then merge into anything else that's waiting for CI checks to pass, then hope the Sauce 20,000ms issue stays away for a while, ha.

(For the record: the issue is that readable-stream 2.3.0 breaks Phantom 1.x due to use of Function.prototype.bind and breaks IE7 and 8 due to pulling in safe-buffer, which uses Object.keys.)

… that fixes Node 0.10 on AppVeyor; if need be, some other fix/workaround can be applied to handle whatever was up with debug without causing this issue
@coveralls
Copy link

Coverage Status

Coverage remained the same at 88.395% when pulling ea57b32 on fix-ci into 1f270cd on master.

@ScottFreeCode
Copy link
Contributor Author

This may end up superseded by nodejs/readable-stream#295 and feross/safe-buffer#15

@ScottFreeCode
Copy link
Contributor Author

If we do end up specifying version 2.2.11 or 2.2.x of readable-stream ourselves as this PR does, I'd really prefer a lockfile over this quick hack. I threw this together without trying to figure out how to create a lockfile that uses an older-than-latest version of a dependency for the time it's created, and without waiting to follow up on the recent concerns as to whether lockfiles are workable for Mocha.

… incompatibilities introduced by 2.3.0 on June 19th
@boneskull boneskull merged commit 2408d90 into master Jul 26, 2017
@boneskull boneskull deleted the fix-ci branch July 26, 2017 06:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: browser browser-specific
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants