Avoids using Array.prototype.includes since it is not avaialble in no…

[MiguelMadero]

Fixes #3138

[MiguelMadero]

The test failures seem unrelated to my changes. I checked out master and it fails locally as well :(
Are these tests flaky? This is the first time for me running it and sending a PR. Can someone help me decipher the issue here? I manually tested this version with node 6 and global installs still work fine.

[arcanis]

Thanks! I think those tests are flaky, yes. We're working on it :(

[Turbo87]

@arcanis do you think it would be possible to do a quick bugfix release including this fix? right now all Node 4 builds on Travis CI that use yarn are broken because Travis will try to install the most recent version.

[MiguelMadero]

@Turbo87 while I think it's important to have the latest yarn and I would also like a release with this changes, the following installation step is working for us to pin yarn to 0.22.0

  - curl -o- -L https://yarnpkg.com/install.sh | bash -s -- --version 0.22.0

[Turbo87]

@MiguelMadero I know, but then you'd have to explicitly add the yarn installation instructions to your TravisCI config, but Travis already automatically detects the existance of a yarn.lock file and will install and use yarn then unless you overwrite those instructions. I'd personally rather keep using the defaults instead of having to touch the config in every one of my projects.

[MiguelMadero]

Agreed. Just a different workaround than updating the same file to use node 6.

…

On Fri, Apr 21, 2017 at 1:01 AM Tobias Bieniek ***@***.***> wrote: @MiguelMadero <https://github.com/MiguelMadero> I know, but then you'd have to explicitly add the yarn installation instructions to your TravisCI config, but Travis already automatically detects the existance of a yarn.lock file and will install and use yarn then unless you overwrite those instructions. I'd personally rather keep using the defaults instead of having to touch the config in every one of my projects. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3139 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC5HNcoPrpKNyJisjsZMdzSYn13X5OQks5ryGJlgaJpZM4M9TdN> .