An in-range update of core-js is breaking the build 🚨

[greenkeeper]

Version 2.5.0 of core-js just got published.

Branch	Build failing 🚨
Dependency	core-js
Current Version	2.4.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

core-js is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 99 commits.

• 63ae52d 2.5.0
• 998f32e update eslint
• 9025b48 add .of and .from methods on collection constructors to readme
• 20f055b add Array#flatten and Array#flatMap to readme
• 860efb6 fix a typo
• b9203ee update list of iterable DOM collections in readme
• b4c2e5e remove some unused variables, update changelog
• fc32be8 add Promise#try to readme
• ea82fd9 remove caching Function#name, fix #296
• fd850c3 add Promise#finally to readme
• a41dd09 fix IE11 WeakMap frozen keys after zloirock/core-js@a69f577
• 09f45b6 remove tests of excess DOM collections methods - FF have it, I don't think that removing those methods in core-js make sense
• d230280 fix the list of whitespaces in the Number constructor test
• 7c39430 move Array#flatten and Array#flatMap to stage 1 per July TC39 meeting
• d35736f move Promise#finally to stage 3 per July TC39 meeting

There are 99 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 2.4.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.