core-js-compat
Advanced tools
Changelog
ArrayBuffer
s are non-extensible, but Object.isExtensible
does not report it:
Object.{ isExtensible, isSealed, isFrozen }
and Reflect.isExtensible
ArrayBuffer
s as collections keysObject#toString
on AggregateError
in IE10-WeakMap
in IE8-.findLast
methods family marked as supported from Chrome 97web.
modulesChangelog
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
and RegExp
well-known symbols access that could be patchedError
stack from extra entries experimentally added to AggregateError
, #996, in case lack of problems it will be extended to other casesSymbol
support, new well-known symbols created with usage Symbol.for
for ensuring the same keys in different realms, #998process
polyfill bug that incorrectly reports V8 version that's used in some cases of core-js
feature detectionmessage
AggregateError
argumentMath.scale
, a spec draft bugcore-js-builder
work in NodeJS 17, added a workaround of webpack
+ NodeJS 17 issueChangelog
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.