An in-range update of core-js is breaking the build π¨
greenkeeper opened this issue Β· 3 comments
The dependency core-js was updated from 3.1.4
to 3.2.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 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
Release Notes for 3.2.0 - 2019.08.09
Promise.allSettled
moved to stable ES, per July TC39 meetingPromise.any
moved to stage 2,.errors
property ofAggregateError
instances maked non-enumerable, per July TC39 meetingusing
statement proposal moved to stage 2, addedSymbol.asyncDispose
, per July TC39 meeting- Added
Array.isTemplateObject
stage 2 proposal, per June TC39 meeting - Added
Map#updateOrInsert
stage 1 proposal, per July TC39 meeting - Added a fix for
Math.hypot
V8 7.7 bug, since it's still not stable without adding results tocore-js-compat
- Added a workaround for APIs where not possible to replace broken native
Promise
, #579 - added.finally
and patched.then
to / on nativePromise
prototype - Fixed crashing of Opera Presto, #595
- Fixed incorrect early breaking of
{ Map, Set, WeakMap, WeakSet }.deleteAll
- Fixed some missed dependencies in entry points
- Added compat data for Node 12.5, FF 67, Safari 13
- Added support of
DISABLE_OPENCOLLECTIVE
env variable topostinstall
script - Removed
core-js-pure
dependency fromcore-js-compat
, #590 - Fixed generation of
core-js-compat
on Windows, #606
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 π΄
Issue-Label Bot is automatically applying the label bug
to this issue, with a confidence of 0.90. Please mark this comment with π or π to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
After pinning to 3.1.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
dependency
core-js was updated from3.2.0
to3.2.1
.
Your tests are still failing with this version. Compare changes
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