chore(deps): update dependency core-js to v3.25.5 #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.3.5
->3.25.5
Release Notes
zloirock/core-js
v3.25.5
Compare Source
v3.25.4
Compare Source
Function.prototype.{ call, apply, bind }
on string methods, #1128[Serializable]
and[Transferable]
objects in thestructuredClone
polyfill. Mainly, for better error messages if polyfilling of cloning such types is impossibleArray.prototype.{ group, groupToMap }
marked as supported from V8 ~ Chromium 108v3.25.3
Compare Source
Array.prototype.groupToMap
in the pure version for returning wrappedMap
instancesArray.prototype.{ findLast, findLastIndex }
in/stage/4
entryv3.25.2
Compare Source
document.all
as a callable in some missed casesv3.25.1
Compare Source
sideEffects
field tocore-js-pure
package.json
for better tree shaking, #1117semver
dependency fromcore-js-compat
semver
package (ironically) added a breaking change and dropped NodeJS 8 support in the minor7.1
version, after thatsemver
incore-js-compat
was pinned to7.0
since for avoiding breaking changes it should support NodeJS 8. However, sincecore-js-compat
is usually used with other packages that usesemver
dependency, it causes multiple duplication ofsemver
in dependencies. So I decided to removesemver
dependency and replace it with a couple of simple helpers.v3.25.0
Compare Source
Object.prototype.__proto__
polyfilldocument.all
as an object in some missed cases, see ECMAScript Annex B 3.6%WrapForValid(Async)IteratorPrototype%.return
, proposal-iterator-helpers/215.return
in%IteratorHelperPrototype%.return
, #1116value
should be created beforedone
).length
settingArrayBuffer.length
in V8 ~ Chrome 27-WeakMap
for internal states with multiplecore-js
copiesFileList
in thestructuredClone
polyfill extended to some more old engines versionsTypeError
incore-js-compat
/core-js-builder
in case of passing invalid module names / filters for avoiding unexpected result, related to #1115esmodules
core-js-compat
/core-js-builder
targetv3.24.1
Compare Source
IS_BROWSER
detection to avoid a false positive withjsdom
, #1110@@​species
support inPromise
in some old engines{ Array, %TypedArray% }.prototype.{ findLast, findLastIndex }
marked as shipped in FF104v3.24.0
Compare Source
.asIndexedPairs
renamed to.indexed
, proposal-iterator-helpers/183:Iterator.prototype.asIndexedPairs
->Iterator.prototype.indexed
AsyncIterator.prototype.asIndexedPairs
->AsyncIterator.prototype.indexed
%AsyncFromSyncIteratorPrototype%
inAsyncIterator.from
andIterator.prototype.toAsync
, proposal-iterator-helpers/182, proposal-iterator-helpers/202%WrapForValidAsyncIteratorPrototype%.next
, proposal-iterator-helpers/197%WrapForValid(Async)IteratorPrototype%.next
, proposal-iterator-helpers/197 and proposal-iterator-helpers/205.next
/.return
to an underlying iterator by the extended iterator protocol, a part of proposal-iterator-helpers/194.throw
methods removed from all wrappers / helpers prototypes, a part of proposal-iterator-helpers/194{ Iterator, AsyncIterator }.prototype.flatMap
proxy iterators on.return
, proposal-iterator-helpers/195RangeError
onNaN
in{ Iterator, AsyncIterator }.prototype.{ drop, take }
, proposal-iterator-helpers/181%TypedArray%.prototype.toSpliced
method removed from the change array by copy proposal and marked as obsolete incore-js
, proposal-change-array-by-copy/88Promise
withunhandledrejection
event support (browser style) in Deno < 1.24core-js-compat
/core-js-builder
and added compat data for them:bun
), compat data for 0.1.1-0.1.5, #1103hermes
), compat data for 0.1-0.11, #1099oculus
), compat data mapping for 3.0-22.0, #1098v3.23.5
Compare Source
structuredClone
feature detection, #1106v3.23.4
Compare Source
core-js
structuredClone
bugs (1774866 (fixed in FF104) and 1777321 (still not fixed)) that now can clone errors, but.stack
of the clone is an empty string{ Map, WeakMap }.prototype.emplace
logic, #1102v3.23.3
Compare Source
%TypedArray%.prototype.toSpliced
following proposal-change-array-by-copy/89v3.23.2
Compare Source
%TypedArray%
constructors in new methods, #1092 (comment)v3.23.1
Compare Source
core-js
copies, #1091v
flag toRegExp.prototype.flags
implementation in case if current V8 bugs will not be fixed before this flag implementationv3.23.0
Compare Source
Array
find from last moved to the stable ES, according to June 2022 TC39 meeting:Array.prototype.findLast
Array.prototype.findLastIndex
%TypedArray%.prototype.findLast
%TypedArray%.prototype.findLastIndex
Array
grouping proposal renamed, according to June 2022 TC39 meeting:Array.prototype.groupBy
->Array.prototype.group
Array.prototype.groupByToMap
->Array.prototype.groupToMap
%TypedArray%.prototype.with
following proposal-change-array-by-copy/86, according to June 2022 TC39 meetingSymbol.metadataKey
replacesSymbol.metadata
Array.prototype.push
polyfill with some fixes for modern enginesArray.prototype.unshift
polyfill with some fixes for modern enginesRegExp.prototype.flags
in the actual version of V8Math
andNumber
constantsArrayBufferDetaching
protector cell invalidation and performance degradation onstructuredClone
feature detection, one more case of #679structuredClone
that can not cloneDOMException
(just in case for future versions that will fix other issues)v3.22.8
Compare Source
ToBigInt
/ToNumber
conversion of the argument passed to%TypedArray%.prototype.fill
in V8 ~ Chrome < 59, Safari < 14.1, FF < 55, Edge <=18DeletePropertyOrThrow
in IE9-TypeError
instead ofError
) on incorrectexec
result inRegExp.prototype.test
polyfill{ actual, full, features }/typed-array/at
entriesv3.22.7
Compare Source
v3.22.6
Compare Source
ToNumber
conversion on arguments ofMath.{ fround, trunc }
polyfillsArray.prototype.includes
marked as fixed in FF102v3.22.5
Compare Source
.prototype
is non-writable.prototype
is not definedstruturedClone
that returnsnull
if cloned object contains multiple references to one errorv3.22.4
Compare Source
.length
of polyfilled functions even in compressed code (excepting some ancient engines).name
of polyfilled accessors (excepting some ancient engines)ToString
conversion of polyfilled accessorsv3.22.3
Compare Source
Array.prototype.includes
broken on sparse arraysv3.22.2
Compare Source
URLSearchParams
in IE8- that was broken in the previous release__lookupGetter__
entriesv3.22.1
Compare Source
RegExp
flags handlingfetch
APIv3.22.0
Compare Source
Array
by copy proposal:/actual/
entry points for methods from this proposalArray.prototype.toSpliced
throws aTypeError
instead ofRangeError
if the result length is more thanMAX_SAFE_INTEGER
, proposal-change-array-by-copy/70atob
/btoa
fixes:atob
does not ignore spaces, node/42530atob
does not validate encoding, node/42646/full/
namespace as the replacement for/features/
since it's more descriptive in context of the rest namespaces (/es/
⊆/stable/
⊆/actual/
⊆/full/
)%TypedArray%.prototype.groupBy
was removed from theArray
grouping proposal a long time ago. We can't completely remove this method since it's a breaking change. But this proposal has been promoted to stage 3 - so the proposal should be promoted without this method, this method should not be available in/actual/
entries - but it should be available in early-stage entries to avoid breakage.Error
features with wrappedError
constructors, #1061null
andundefined
allowed as the second argument ofstructuredClone
, #1056core-js-compat
->core-js-builder
->core-js-bundle
output. That mean that if the output contains, for example,es.object.has-own
, the legacy reference to it,esnext.object.has-own
, no longer added.core-js-builder
andcore-js-compat
, now it'smodules
andexclude
optionstargets
option ofcore-js-compat
means that thetargets
filter just will not be applied, so the result will contain modules required for all possible engines.stack
property onDOMException
marked as supported from Deno 1.15v3.21.1
Compare Source
Array.prototype.{ groupBy, groupByToMap }
implementationcore-js-compat
targets parser transforms engine names to lower caseatob
/btoa
marked as fixed in NodeJS 17.5v3.21.0
Compare Source
atob
btoa
v3.20.3
Compare Source
Function#bind
polyfills, uses only nativeFunction#bind
in the internalsstructuredClone
should throw an error if no arguments passed__core-js_shared__
v3.20.2
Compare Source
Object.{ defineProperty, defineProperties }
bug, Babel issue%TypedArray%.prototype.set
bugs, affects modern engines (like Chrome < 95 or Safari < 14.1)v3.20.1
Compare Source
Promise.prototype.then
, #1026v3.20.0
Compare Source
structuredClone
method from the HTML spec, see MDNhtml/5749
DOMException
polyfill, the Web IDL spec, see MDNDOMException
and its attributes polyfills with fixes of many different engines bugsDOMException#stack
property polyfill in engines that should have itDOMException
implementations where it's possible (for example, in old NodeJS where it's not exposed as global)cause
on all Error typesError.prototype.toString
method polyfill with fixes of many different bugs of JS enginesNumber.prototype.toExponential
method polyfill with fixes of many different bugs of JS enginesArray
grouping proposal:Array.prototype.groupByToMap
method@@​species
supportArray
by copy stage 2 proposal:Array.prototype.toReversed
Array.prototype.toSorted
Array.prototype.toSpliced
Array.prototype.with
%TypedArray%.prototype.toReversed
%TypedArray%.prototype.toSorted
%TypedArray%.prototype.toSpliced
%TypedArray%.prototype.with
Iterator.prototype.toAsync
method from the iterator helpers stage 2 proposalArray.fromAsync
proposal moved to stage 2String.cooked
stage 1 proposal:Function.prototype.unThis
stage 0 proposalFunction.{ isCallable, isConstructor }
stage 0 proposal:Function.isCallable
Function.isConstructor
String#at
after loading obsoleteString#at
proposal module, #1019Array.prototype.{ values, @​@​iterator }.name
in V8 ~ Chrome 45-core-js/actual/**
namespacev3.19.3
Compare Source
URLSearchParams
iterator.next
that should be enumerable by the specSubscription
v3.19.2
Compare Source
RegExp#sticky
flag, #1008, #1015Function#name
polyfill, #1010, thanks @ildar-shaimordanovArray.prototype[@​@​species]
URL
andURLSearchParams
v3.19.1
Compare Source
ArrayBuffer
s are non-extensible, butObject.isExtensible
does not report it:Object.{ isExtensible, isSealed, isFrozen }
andReflect.isExtensible
ArrayBuffer
s as collections keysObject#toString
onAggregateError
in IE10-WeakMap
in IE8-.findLast
methods family marked as supported from Chrome 97web.
modulesv3.19.0
Compare Source
core-js
for preventing possible cases of breaking / observing the internal state by patching / deleting of them.call
/.apply
prototype methods that could be patchedinstanceof
operator - implicit.prototype
/@@​hasInstance
access that could be patchedRegExp#test
,String#match
and some over methods - implicit.exec
andRegExp
well-known symbols access that could be patchedError
stack from extra entries experimentally added toAggregateError
, #996, in case lack of problems it will be extended to other casesSymbol
support, new well-known symbols created with usageSymbol.for
for ensuring the same keys in different realms, #998process
polyfill bug that incorrectly reports V8 version that's used in some cases ofcore-js
feature detectionmessage
AggregateError
argumentMath.scale
, a spec draft bugcore-js-builder
work in NodeJS 17, added a workaround ofwebpack
+ NodeJS 17 issuev3.18.3
Compare Source
AggregateError
constructor that should containError
constructorAggregateError.prototype
properties descriptorsInstallErrorCause
internal operationObject.hasOwn
marked as supported from Safari 15.1v3.18.2
Compare Source
{ Array, %TypedArray% }.fromAsync
errors moved to the promise, per the latest changes of the spec draftToInteger(OrInfinity)
operation returns+0
for-0
argument, ES2020+ updateNumber
constructor wrapperString.raw
with extra argumentsv3.18.1
Compare Source
String.prototype.substr
feature detection and compat data.forEach
from prototypes of some DOM collections where it shouldn't be, #988, #987, thanks @moorejscause
toAggregateError
constructor implementation (still without adding to the feature detection).at
and.findLast
methods marked as supported in Safari TPv3.18.0
Compare Source
Array.fromAsync
stage 1 proposal:Array.fromAsync
%TypedArray%.fromAsync
.name
and.toString()
on polyfilled functions improved in many different casesIsConstructor
andIsCallable
checksGetMethod
operationparseInt
/parseFloat
with boxed symbolses.array.{ index-of, last-index-of }
compat datav3.17.3
Compare Source
%IteratorPrototype%
and%AsyncIteratorPrototype%
in the futureDOMTokenList.prototype.{ forEach, @​@​iterator, keys, values, entries }
in old WebKit versions whereelement.classList
is not an instance of globalDOMTokenList
v3.17.2
Compare Source
v3.17.1
Compare Source
modules-by-versions
datav3.17.0
Compare Source
Object.prototype.hasOwnProperty
(Object.hasOwn
) proposal moved to the stable ES, per August 2021 TC39 meeting.at
) proposal moved to the stable ES, per August 2021 TC39 meetingString.prototype.at
. It was not exposed because of the conflict with the alternative obsolete proposal (that will be completely removed in the next major version). For the backward compatibility, in the case of loading this proposal, it will be overwritten.v3.16.4
Compare Source
AsyncFromSyncIterator
made stricter, related mainly toAsyncIterator.from
andAsyncIterator.prototype.flatMap
.next
arguments in(Async)Iterator
methods is aligned with the current spec draft (mainly - ignoring the first passed to.next
argument in built-in generators).next
,.return
,.throw
methods onAsyncIterator
helpers proxy iterators aligned with the current spec draft (built-in async generators) (mainly - some early errors moved to returned promises)v3.16.3
Compare Source
CreateAsyncFromSyncIterator
semantic inAsyncIterator.from
, related to #765Object.prototype
, #973v3.16.2
Compare Source
Object.create(null)
on WSH, #970v3.16.1
Compare Source
v3.16.0
Compare Source
Array
find from last proposal moved to the stage 3, July 2021 TC39 meetingArray
filtering stage 1 proposal:Array.prototype.filterReject
replacesArray.prototype.filterOut
%TypedArray%.prototype.filterReject
replaces%TypedArray%.prototype.filterOut
Array
grouping stage 1 proposal:Array.prototype.groupBy
%TypedArray%.prototype.groupBy
@@​toPrimitive
in some cases ofToPrimitive
internal logic made stricterRequest
with polyfilledURLSearchParams
, #965Object.create(null)
on WSH, #966RegExp#exec
Date.prototype.getYear
feature detectiondeno
target incore-js-compat
/core-js-builder
Object.hasOwn
marked as supported from V8 9.3 and FF92Date.prototype.getYear
marked as not supported in IE8-summary
option tocore-js-builder
, see more info in theREADME
, #910v3.15.2
Compare Source
zone.js
loaded beforecore-js
, #953v3.15.1
Compare Source
RegExp
constructor, #948v3.15.0
Compare Source
RegExp
named capture groups polyfill, #521, #944RegExp
dotAll
flag polyfill, #792, #944escape
unescape
String.prototype.substr
Date.prototype.getYear
Date.prototype.setYear
Date.prototype.toGMTString
URL
polyfillrhino
target incore-js-compat
/core-js-builder
, added compat data forrhino
1.7.13, #942, thanks @gausie.at
marked as supported from FF90v3.14.0
Compare Source
{ Array, %TypedArray% }.prototype.sort
, #769, #941Safari
14.0-%TypedArray%.prototype.sort
validation of arguments bug.at
marked as supported from V8 9.2v3.13.1
Compare Source
get-own-property-symbols
third-partySymbol
polyfill if it's used since it causes a stack overflow, #774Object.prototype
accessors methods in WebKit ~ Android 4.0, #232v3.13.0
Compare Source
Object#hasOwnProperty
(Object.hasOwn
) proposal moved to the stage 3, May 2021 TC39 meetingv3.12.1
Compare Source
Function#toString
with multiplecore-js
instancesString#split
polyfill problems in V8 5.1v3.12.0
Compare Source
Symbol.metadata
for decorators stage 2 proposalSymbol.matcher
for pattern matching stage 1 proposalString(Symbol())
bug, #933v3.11.3
Compare Source
Promise#{ catch, finally }
returns polyfilledPromise
instances when it's requiredv3.11.2
Compare Source
Promise
bug, #932Promise#then
of incorrect nativePromise
implementations with correct subclassing no longer wrappedPromise
feature detection, removed unhandled rejection tracking check in non-browser non-node platformsv3.11.1
Compare Source
instanceof Promise
and.constructor === Promise
work with polyfilledPromise
for all native promise-based APIs%TypedArray%
static methods, #564v3.11.0
Compare Source
Object#hasOwnProperty
stage 2 proposalObject.hasOwn
methodRegExp
constructor problem with multiple globalcore-js
instancesv3.10.2
Compare Source
URL
andURLSearchParams
marked as supported from Safari 14.0v3.10.1
Compare Source
RegExp#split
problems in old engines, #751, #919v3.10.0
Compare Source
Array
find from last proposal moved to the stage 2, March TC39 meetingRegExp#exec
problems in some old engines, #920v3.9.1
Compare Source
NumericRangeIterator
as toStringTag instead ofRangeIterator
in{ Number, BigInt }.range
iterator, per this PRv3.9.0
Compare Source
Array
find from last stage 1 proposalArray#findLast
Array#findLastIndex
%TypedArray%#findLast
%TypedArray%#findLastIndex
%TypedArray%#uniqueBy
method for array deduplication stage 1 proposal%TypedArray%#uniqueBy
ToLength
detection from array methods feature detection which could cause hanging FF11-21 and some versions of old WebKit, #764core-js-bundle
usesterser
instead ofuglify-js
v3.8.3
Compare Source
Iterator
, #906v3.8.2
Compare Source
String#replaceAll
, #900Promise.any
andPromise.allSettled
entriesv3.8.1
Compare Source
%TypedArray%
methods onBigInt
arraysNumber
constructor wrapperv3.8.0
Compare Source
Array#at
%TypedArray%#at
Number.range
stage 1 proposalNumber.range
BigInt.range
Array#filterOut
%TypedArray%#filterOut
Array#uniqueBy
String#at
for preventing breakage code which use obsoleteString#at
proposal polyfill(es|stable)/instance/replace-all
entriescore-js-builder
blacklist
option in favor ofexclude
v3.7.0
Compare Source
String#replaceAll
moved to the stable ES, per June TC39 meetingPromise.any
andAggregateError
moved to the stable ES, per July TC39 meetingReflect[@​@​toStringTag]
, per July TC39 meetingArray#{ reduce, reduceRight }
in Chrome 80-82 because of a bug, #766upsert
proposal,{ Map, WeakMap }#emplace
replace{ Map, WeakMap }#upsert
, these obsolete methods will be removed in the next major releaseAggregateError#errors
is own data propertyprocess.nextTick
have a less priority thanPromise
in the microtask implementation, #855MutationObserver
, but withoutdocument
, #865, #866core-js-builder
with an empty (after the targets engines or another filtration) modules list, [#822](https://togithConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.