This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
fix(deps): update dependency core-js to v3.29.1 #127
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/core-js-3.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
December 10, 2020 13:54
3b4f79c
to
8813156
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.8.0
fix(deps): update dependency core-js to v3.8.1
Dec 10, 2020
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
January 7, 2021 15:57
8813156
to
48b3a76
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.8.1
fix(deps): update dependency core-js to v3.8.2
Jan 7, 2021
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
January 24, 2021 14:59
48b3a76
to
27bfb4f
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.8.2
fix(deps): update dependency core-js to v3.8.3
Jan 24, 2021
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
April 26, 2021 17:36
27bfb4f
to
d51502e
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.8.3
fix(deps): update dependency core-js to v3.11.0
Apr 26, 2021
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
May 9, 2021 21:19
d51502e
to
184fa87
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.11.0
fix(deps): update dependency core-js to v3.12.1
May 9, 2021
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
June 6, 2021 20:46
184fa87
to
ec05f9a
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.12.1
fix(deps): update dependency core-js to v3.14.0
Jun 6, 2021
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
October 18, 2021 19:29
ec05f9a
to
fa9ee20
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.14.0
fix(deps): update dependency core-js to v3.18.3
Oct 18, 2021
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
March 7, 2022 09:08
fa9ee20
to
125d6a5
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.18.3
fix(deps): update dependency core-js to v3.21.1
Mar 7, 2022
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
April 25, 2022 01:57
125d6a5
to
a5c54e1
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.21.1
fix(deps): update dependency core-js to v3.22.2
Apr 25, 2022
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
May 16, 2022 01:13
a5c54e1
to
51faf6d
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.22.2
fix(deps): update dependency core-js to v3.22.5
May 16, 2022
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
June 18, 2022 18:06
51faf6d
to
ab177ea
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.22.5
fix(deps): update dependency core-js to v3.23.1
Jun 18, 2022
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
June 23, 2022 22:14
ab177ea
to
9b822da
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.23.1
fix(deps): update dependency core-js to v3.23.2
Jun 23, 2022
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
September 25, 2022 18:53
9b822da
to
a47b6a3
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.23.2
fix(deps): update dependency core-js to v3.25.2
Sep 25, 2022
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
November 20, 2022 07:21
a47b6a3
to
c7d87a1
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.25.2
fix(deps): update dependency core-js to v3.26.1
Nov 20, 2022
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
March 18, 2023 23:51
c7d87a1
to
3f361c0
Compare
renovate
bot
changed the title
fix(deps): update dependency core-js to v3.26.1
fix(deps): update dependency core-js to v3.29.1
Mar 18, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.6.5
->3.29.1
Release Notes
zloirock/core-js
v3.29.1
Compare Source
ToString
conversion / built-ins nature of some accessorsString.prototype.{ isWellFormed, toWellFormed }
marked as supported from V8 ~ Chrome 111v3.29.0
Compare Source
URLSearchParams.prototype.size
getter, url/734ArrayBuffer
s in thestructuredClone
polyfill/(stable|actual|full)/instance/unshift
entries, #1207Set
methods proposal marked as supported from Bun 0.5.7String.prototype.toWellFormed
marked as fixed from Bun 0.5.7v3.28.0
Compare Source
3.28.0 - 2023.02.14
v3.27.2
Compare Source
Set
methods proposal updates:Set
-like objects on early exit, proposal-set-methods/85webpack
dev server bug on IE global methods, #1161String.{ raw, cooked }
error with empty template arrayError.captureStackTrace
instead of stack parsing in new error classes / wrappers where it's possiblePromise.{ allSettled, any }
feature detection, Hermes issueArray
by copy proposal marked as supported from V8 ~ Chrome 110self
marked as fixed in Deno 1.29.3, deno/17362core-js-bundle
v3.27.1
Compare Source
WeakMap
keysString.dedent
in MS Edgev3.27.0
Compare Source
Iterator
Iterator.from
Iterator.prototype.drop
Iterator.prototype.every
Iterator.prototype.filter
Iterator.prototype.find
Iterator.prototype.flatMap
Iterator.prototype.forEach
Iterator.prototype.map
Iterator.prototype.reduce
Iterator.prototype.some
Iterator.prototype.take
Iterator.prototype.toArray
Iterator.prototype.toAsync
Iterator.prototype[@​@​toStringTag]
AsyncIterator
AsyncIterator.from
AsyncIterator.prototype.drop
AsyncIterator.prototype.every
AsyncIterator.prototype.filter
AsyncIterator.prototype.find
AsyncIterator.prototype.flatMap
AsyncIterator.prototype.forEach
AsyncIterator.prototype.map
AsyncIterator.prototype.reduce
AsyncIterator.prototype.some
AsyncIterator.prototype.take
AsyncIterator.prototype.toArray
AsyncIterator.prototype[@​@​toStringTag]
/actual/
entries, unconditional forced replacement disabled for features that survived to Stage 3.from
accept strings,.flatMap
throws on strings returned from the callback, proposal-iterator-helpers/244, proposal-iterator-helpers/250.from
and.flatMap
throws on non-object iterators, proposal-iterator-helpers/253Set
methods proposal:Set.prototype.intersection
Set.prototype.union
Set.prototype.difference
Set.prototype.symmetricDifference
Set.prototype.isSubsetOf
Set.prototype.isSupersetOf
Set.prototype.isDisjointFrom
Set
-like objects as an argument, not all iterablesSet
s asthis
, no@@​species
support, and other minor changes/actual/
entries, unconditional forced replacement changed to feature detection/actual/
namespace)/full/
namespace), those methods are available with fallbacks to old semantics (in addition toSet
-like, they accept iterable objects). This behavior will be removed from the next major releaseString.prototype.isWellFormed
String.prototype.toWellFormed
/actual/
entries, disabled unconditional forced replacementusing
statement" and splitted into 2 (sync and async) proposalsSymbol.dispose
Symbol.asyncDispose
SuppressedError
DisposableStack
DisposableStack.prototype.dispose
DisposableStack.prototype.use
DisposableStack.prototype.adopt
DisposableStack.prototype.defer
DisposableStack.prototype.move
DisposableStack.prototype[@​@​dispose]
AsyncDisposableStack
AsyncDisposableStack.prototype.disposeAsync
AsyncDisposableStack.prototype.use
AsyncDisposableStack.prototype.adopt
AsyncDisposableStack.prototype.defer
AsyncDisposableStack.prototype.move
AsyncDisposableStack.prototype[@​@​asyncDispose]
Iterator.prototype[@​@​dispose]
AsyncIterator.prototype[@​@​asyncDispose]
/actual/
namespace entries for Stage 3 proposalString.dedent
stage 2 proposalString.dedent
react-native
target for React Native with bundled Hermes.oculus
target was renamed toquest
.opera_mobile
target name is confusing since it contains data for the Chromium-based Android version, but iOS Opera is Safari-based. Soopera_mobile
target was renamed toopera-android
.android
target name is also confusing for someone - that means Android WebView, some think thinks that it's Chrome for Android, but they have some differences. For avoiding confusion, addedchrome-android
target.firefox-android
target.oculus
andopera_mobile
fields are available in the compat data till the next major release.Array.fromAsync
marked as supported from Bun 0.3.0String.prototype.{ isWellFormed, toWellFormed }
marked as supported from Bun 0.4.0Array
by copy proposal marked as supported from Deno 1.27, deno/16429{ Map, WeakMap }.prototype.emplace
became stricter by the spec draft@@​species
pattern) of some.prototype
methods from the new collections methods proposal and theArray
deduplication proposal that most likely will not be implemented since it contradicts the current TC39 policyNumber
constructor, #1154, #1155, thanks @trososset(Timeout|Interval|Immediate)
extra arguments fix for Bun 0.3.0- (similarly to IE9-), bun/1633structuredClone
, #1156v3.26.1
Compare Source
Array.fromAsync
since it's on Stage 3function-uncurry-this
helper where it's not required - minor optimization and preventing problems in some broken environments, a workaround of #1141Array.prototype.{ group, groupToMap }
in V8 ~ Chromium 108, proposal-array-grouping/44v3.26.0
Compare Source
Array.fromAsync
proposal:%Array.prototype.values%
usage in array-like branch, proposal-array-from-async/30String.prototype.isWellFormed
String.prototype.toWellFormed
AsyncIterator
helpers, proposal-iterator-helpers/239{ Iterator, AsyncIterator }.prototype.flatMap
supports returning both - iterables and iterators, proposal-iterator-helpers/233.next
in missed cases of{ Iterator, AsyncIterator }.from
, proposal-iterator-helpers/232self
polyfill as a part of The Minimum Common Web Platform API, specification, #1118inverse
option tocore-js-compat
, #1119format
option tocore-js-builder
, #1120v3.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 proposalFunction.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
, [#​Configuration
📅 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.