-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of core-js is breaking the build 🚨 #16
Comments
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. |
Your tests are still failing with this version. Compare changes Release Notes for 3.3.1 - 2019.10.13
|
Your tests are still failing with this version. Compare changes Release Notes for 3.3.2 - 2019.10.14
|
Your tests are still failing with this version. Compare changes Release Notes for 3.3.4 - 2019.10.25
|
Your tests are still failing with this version. Compare changes Release Notes for 3.3.5 - 2019.10.29
|
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes Release Notes for 3.4.0 - 2019.11.07
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.1 - 2019.11.12
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.2 - 2019.11.22
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.3 - 2019.11.26
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.4 - 2019.11.27
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.5 - 2019.11.28
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.6 - 2019.12.03
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.7 - 2019.12.03
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.8 - 2019.12.09
|
Your tests are still failing with this version. Compare changes Release Notes for 3.5.0 - 2019.12.12
|
Your tests are still failing with this version. Compare changes Release Notes for 3.6.0 - 2019.12.19
|
Your tests are still failing with this version. Compare changes Release Notes for 3.6.1 - 2019.12.25
|
Your tests are still failing with this version. Compare changes |
The dependency core-js was updated from
3.2.1
to3.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 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.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 releaseglobalThis
moved to stable ES, per October TC39 meetingPromise.any
moved to stage 3, some minor internal changes, per October TC39 meetingString#replaceAll
moved to stage 3, per October TC39 meetingIterator
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
Map#upsert
(Map#updateOrInsert
before) proposalMap#updateOrInsert
renamed toMap#upsert
WeakMap#upsert
Promise
bug, #640URL
constructor in Safari andURLSearchParams
in Chrome 66-, #656Math.hypot
marked as not supported in Chrome 77 since a bug in this method was not fixed before the stable Chrome 77 releaseSymbol.matchAll
inesnext.string.match-all
, #626.next
method once, at the beginning, of the iteration protocolpostinstall
messages only once pernpm i
, #597, thanks @remyFAQ 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 🌴
The text was updated successfully, but these errors were encountered: