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

[greenkeeper[bot]]

The devDependency core-js was updated from 3.2.1 to 3.3.0.

🚨 View failing branch.

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

core-js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/Chimeejs/chimee/builds/597277206?utm_source=github_status&utm_medium=notification)).

---

Release Notes for 3.3.0 - 2019.10.13

• String#{ matchAll, replaceAll } throws an error on non-global regex argument per the decision from TC39 meetings (+ this PR). It's a breaking change, but since it's a breaking change in the ES spec, it's added at the minor release
• globalThis moved to stable ES, per October TC39 meeting
• Promise.any moved to stage 3, some minor internal changes, per October TC39 meeting
• String#replaceAll moved to stage 3, per October TC39 meeting
• Added iterator helpers stage 2 proposal:
  • Iterator
    • Iterator.from
    • Iterator#asIndexedPairs
    • Iterator#drop
    • Iterator#every
    • Iterator#filter
    • Iterator#find
    • Iterator#flatMap
    • Iterator#forEach
    • Iterator#map
    • Iterator#reduce
    • Iterator#some
    • Iterator#take
    • Iterator#toArray
    • Iterator#@@toStringTag
  • AsyncIterator
    • AsyncIterator.from
    • AsyncIterator#asIndexedPairs
    • AsyncIterator#drop
    • AsyncIterator#every
    • AsyncIterator#filter
    • AsyncIterator#find
    • AsyncIterator#flatMap
    • AsyncIterator#forEach
    • AsyncIterator#map
    • AsyncIterator#reduce
    • AsyncIterator#some
    • AsyncIterator#take
    • AsyncIterator#toArray
    • AsyncIterator#@@toStringTag
• Updated Map#upsert (Map#updateOrInsert before) proposal
  • Moved to stage 2, per October TC39 meeting
  • Map#updateOrInsert renamed to Map#upsert
  • Added WeakMap#upsert
  • You can don't pass one of the callbacks
• Added a workaround for iOS Safari MessageChannel + bfcache bug, #624
• Added a workaround for Chrome 33 / Android 4.4.4 Promise bug, #640
• Replaced broken URL constructor in Safari and URLSearchParams in Chrome 66-, #656
• Added compat data for Node up to 12.11, FF 69, Samsung up to 10.2 and Phantom 1.9
• Math.hypot marked as not supported in Chrome 77 since a bug in this method was not fixed before the stable Chrome 77 release
• Fixed unnecessary exposing on Symbol.matchAll in esnext.string.match-all, #626
• Fixed missed cases access the .next method once, at the beginning, of the iteration protocol
• Show similar postinstall messages only once per npm i, #597, thanks @remy

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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

[greenkeeper[bot]]

• The devDependency core-js was updated from 3.3.0 to 3.3.1.

Your tests are still failing with this version. Compare changes

Release Notes for 3.3.1 - 2019.10.13

• Fixed an NPM publishing issue

[greenkeeper[bot]]

• The devDependency core-js was updated from 3.3.1 to 3.3.2.

Your tests are still failing with this version. Compare changes

Release Notes for 3.3.2 - 2019.10.14

• Fixed compatibility of core-js-compat with Node 6 and Yarn, #669

[greenkeeper[bot]]

• The devDependency core-js was updated from 3.3.3 to 3.3.4.

Your tests are still failing with this version. Compare changes

Release Notes for 3.3.4 - 2019.10.25

• Added a workaround of V8 deoptimization which causes serious performance degradation (~20x in my tests) of some RegExp-related methods like String#split, #306
• Added a workaround of V8 deoptimization which causes serious performance degradation (up to 100x in my tests) of Array#splice and slightly Array#{ filter, map }, #677
• Fixed work of fetch with polyfilled URLSearchParams, #674
• Fixed an edge case of String#replaceAll with an empty search value
• Added compat data for Chrome 80
• package-lock.json no longer generated in libraries

[greenkeeper[bot]]

• The devDependency core-js was updated from 3.3.4 to 3.3.5.

Your tests are still failing with this version. Compare changes

Release Notes for 3.3.5 - 2019.10.29

• Added a workaround of V8 deoptimization which causes serious performance degradation (~4x in my tests) of Array#concat, #679
• Added a workaround of V8 deoptimization which causes slightly performance degradation of Promise, #679
• Added (Async)Iterator.prototype.constructor -> (Async)Iterator per this issue
• Added compat data for Chromium-based Edge

[greenkeeper[bot]]

• The devDependency core-js was updated from 3.3.5 to 3.3.6.

Your tests are still failing with this version. Compare changes

Release Notes for 3.3.6 - 2019.11.01

• Don't detect Chakra-based Edge as Chrome in the userAgent parsing
• Fixed inheritance in typed array constructors wrappers, #683
• Added one more workaround for correct work of early fetch implementations with polyfilled URLSearchParams, #680

[greenkeeper[bot]]

• The devDependency core-js was updated from 3.3.6 to 3.4.0.

Your tests are still failing with this version. Compare changes

Release Notes for 3.4.0 - 2019.11.07

• Added well-formed JSON.stringify, ES2019 feature, thanks @ExE-Boss and @WebReflection for the idea
• Fixed Math.signbit, #687, thanks @chicoxyzzy

[greenkeeper[bot]]

• The devDependency core-js was updated from 3.4.0 to 3.4.1.

Your tests are still failing with this version. Compare changes

Release Notes for 3.4.1 - 2019.11.12

• Throw when (Async)Iterator#flatMap mapper returns a non-iterable, per tc39/proposal-iterator-helpers/55 and tc39/proposal-iterator-helpers/59
• Removed own AggregateError#toString, per tc39/proposal-promise-any/49
• Global core-js Promise polyfill passes feature detection in the pure versions
• Fixed indexes in String#replaceAll callbacks
• String#replaceAll marked as supported by FF72

[greenkeeper[bot]]

• The devDependency core-js was updated from 3.4.1 to 3.4.2.

Your tests are still failing with this version. Compare changes

Release Notes for 3.4.2 - 2019.11.22

• Don't use polyfilled symbols as internal uids, a workaround for some incorrect use cases
• String#replaceAll is available only in nightly FF builds
• Improved Promise feature detection for the case of V8 6.6 with multiple core-js copies
• Some internals optimizations
• Added Node 13.2 -> V8 7.9 compat data mapping
• Returned usage of node -e in postinstall scripts