core-js-pure
Advanced tools
Changelog
AggregateError
constructor that should contain Error
constructorAggregateError.prototype
properties descriptorsInstallErrorCause
internal operationObject.hasOwn
marked as supported from Safari 15.1Changelog
{ 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 argumentsChangelog
String.prototype.substr
feature detection and compat data.forEach
from prototypes of some DOM collections where it shouldn't be, #988, #987, thanks @moorejscause
to AggregateError
constructor implementation (still without adding to the feature detection).at
and .findLast
methods marked as supported in Safari TPChangelog
Array.fromAsync
stage 1 proposal:
Array.fromAsync
%TypedArray%.fromAsync
.name
and .toString()
on polyfilled functions improved in many different casesIsConstructor
and IsCallable
checksGetMethod
operationparseInt
/ parseFloat
with boxed symbolses.array.{ index-of, last-index-of }
compat dataChangelog
%IteratorPrototype%
and %AsyncIteratorPrototype%
in the futureDOMTokenList.prototype.{ forEach, @@iterator, keys, values, entries }
in old WebKit versions where element.classList
is not an instance of global DOMTokenList
Changelog
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.Changelog
AsyncFromSyncIterator
made stricter, related mainly to AsyncIterator.from
and AsyncIterator.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 on AsyncIterator
helpers proxy iterators aligned with the current spec draft (built-in async generators) (mainly - some early errors moved to returned promises)