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

Question

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

greenkeeper opened this issue 5 years ago · 18 comments

The dependency core-js was updated from `3.2.0` to `3.2.1`.

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, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ JPProject - PR: 1 errors / 0 warnings
✅ JPProject - PR (Docker files): 0 errors / 0 warnings
✅ JPProject - PR (.NET Core Build): 0 errors / 0 warnings
❌ JPProject - PR (Angular Build): 1 errors / 0 warnings

Release Notes for 3.2.1 - 2019.08.12

Added a workaround for possible recursion in microtasks caused by conflicts with other Promise polyfills, #615

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 🌴

Answer 1 · 2019-10-13T15:30:41.000Z

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

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 2 · 2019-10-13T15:35:46.000Z

The dependency core-js was updated from 3.3.0 to 3.3.1.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

Release Notes for 3.3.1 - 2019.10.13

Fixed an NPM publishing issue

Answer 3 · 2019-10-14T14:12:12.000Z

The dependency core-js was updated from 3.3.1 to 3.3.2.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

Release Notes for 3.3.2 - 2019.10.14

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

Answer 4 · 2019-10-25T11:45:08.000Z

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

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 5 · 2019-10-28T18:20:55.000Z

The dependency core-js was updated from 3.3.4 to 3.3.5.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 6 · 2019-10-31T17:44:35.000Z

The dependency core-js was updated from 3.3.5 to 3.3.6.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 7 · 2019-11-06T22:37:44.000Z

The dependency core-js was updated from 3.3.6 to 3.4.0.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 8 · 2019-11-12T05:45:12.000Z

The dependency core-js was updated from 3.4.0 to 3.4.1.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 9 · 2019-11-21T20:04:36.000Z

The dependency core-js was updated from 3.4.1 to 3.4.2.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 10 · 2019-11-26T14:35:08.000Z

The dependency core-js was updated from 3.4.2 to 3.4.3.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 11 · 2019-11-27T06:57:22.000Z

The dependency core-js was updated from 3.4.3 to 3.4.4.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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-

Answer 12 · 2019-11-27T22:40:41.000Z

The dependency core-js was updated from 3.4.4 to 3.4.5.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 13 · 2019-12-02T17:57:39.000Z

The dependency core-js was updated from 3.4.5 to 3.4.6.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 14 · 2019-12-02T18:20:48.000Z

The dependency 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

Answer 15 · 2019-12-08T21:27:59.000Z

The dependency core-js was updated from 3.4.7 to 3.4.8.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 16 · 2019-12-12T01:16:56.000Z

The dependency core-js was updated from 3.4.8 to 3.5.0.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

Release Notes for 3.5.0 - 2019.12.12

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

Answer 17 · 2019-12-18T23:52:01.000Z

The dependency core-js was updated from 3.5.0 to 3.6.0.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

Answer 18 · 2019-12-25T06:18:41.000Z

The dependency core-js was updated from 3.6.0 to 3.6.1.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

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

The dependency core-js was updated from 3.2.0 to 3.2.1.

The dependency core-js was updated from `3.2.0` to `3.2.1`.