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

[greenkeeper]

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

🚨 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

• ❌ Travis CI - Branch: The build errored.

---

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

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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

[greenkeeper]

• 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]

• 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]

• 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]

• 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]

• 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

[greenkeeper]

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

Your tests are still failing with this version. Compare changes

Release Notes for 3.4.3 - 2019.11.26

• Fixed missed es.json.stringify and some modules from iteration helpers proposal in some entry points
• Added a workaround of String#{ endsWith, startsWith } MDN polyfills bugs, #702
• Fixed .size property descriptor of Map / Set in the pure version
• Refactoring, some internal improvements

[greenkeeper]

• The devDependency core-js was updated from 3.4.3 to 3.4.4.

Your tests are still failing with this version. Compare changes

Release Notes for 3.4.4 - 2019.11.27

• Added feature detection for Safari non-generic Promise#finally bug (critical for core-js-pure)
• Fixed missed esnext.string.code-points in core-js/features/string entry point
• Updated Iterator proposal feature detection for the case of non-standard Iterator in FF44-

[greenkeeper]

• The devDependency core-js was updated from 3.4.4 to 3.4.5.

Your tests are still failing with this version. Compare changes

Release Notes for 3.4.5 - 2019.11.28

• Detect incorrect order of operations in Object.assign, MS Edge bug
• Detect usage of ToLength in Array#{ filter, map }, FF48-49 and MS Edge 14- issues
• Detect incorrect MS Edge 17-18 Reflect.set which allows setting the property to object with non-writable property on the prototype
• Fixed inspectSource helper with multiple core-js copies and some related features like some edge cases of Promise feature detection

[greenkeeper]

• The devDependency core-js was updated from 3.4.5 to 3.4.6.

Your tests are still failing with this version. Compare changes

Release Notes for 3.4.6 - 2019.12.03

• Improved iOS compat data - added missed mapping iOS 12.2 -> Safari 12.1, added bug fixes from patch releases
• Added Safari 13.1 compat data
• Added missed in core-js-compat helpers ie_mob normalization
• Normalize the result of getModulesListForTargetVersion core-js-compat helper
• Improved CI detection in the postinstall script, #707

[greenkeeper]

• The devDependency core-js was updated from 3.4.6 to 3.4.7.

Your tests are still failing with this version. Compare changes

Release Notes for 3.4.7 - 2019.12.03

• Fixed an NPM publishing issue

[greenkeeper]

• The devDependency core-js was updated from 3.4.7 to 3.4.8.

Your tests are still failing with this version. Compare changes

Release Notes for 3.4.8 - 2019.12.09

• Added one more workaround for broken in previous versions inspectSource helper, #719
• Added Opera Mobile compat data
• Updated Samsung Internet, iOS, old Node and Android compat data mapping
• es.string.match-all marked as completely supported in FF73
• Generate core-js-compat/modules since often we need just the list of core-js modules

[greenkeeper]

• The devDependency core-js was updated from 3.4.8 to 3.5.0.

Your tests are still failing with this version. Compare changes

Release Notes for 3.5.0 - 2019.12.12

• Added object iteratoration stage 1 proposal:
  • Object.iterateKeys
  • Object.iterateValues
  • Object.iterateEntries

[greenkeeper]

• The devDependency core-js was updated from 3.5.0 to 3.6.0.

Your tests are still failing with this version. Compare changes

Release Notes for 3.6.0 - 2019.12.19

• Added support of sticky (y) RegExp flag, #372, #732, #492, thanks @cvle and @nicolo-ribaudo
• Added RegExp#test delegation to RegExp#exec, #732, thanks @cvle
• Fixed some cases of Object.create(null) in IE8-, #727, #728, thanks @aleen42
• Allowed object of minimum environment versions as core-js-compat and core-js-builder targets argument
• Allowed corresponding to Babel targets.esmodules, targets.browsers, targets.node options in core-js-compat and core-js-builder
• Engines in compat data and results of targets parsing sorted alphabetically
• Fixed features/instance/match-all entry compat data
• Fixed Array.prototype[@@unscopables] descriptor (was writable)
• Added Samsung Internet 11 compat data mapping

[greenkeeper]

• The devDependency core-js was updated from 3.6.0 to 3.6.1.

Your tests are still failing with this version. Compare changes

Release Notes for 3.6.1 - 2019.12.25

• Fixed a bug related Symbol with multiple copies of core-js (for 3.4.2-3.6.0), #736
• Refactored some tools

[greenkeeper]

• The devDependency core-js was updated from 3.6.4 to 3.6.5.

Your tests are still failing with this version. Compare changes