core-js-compat
Advanced tools
Changelog
URLSearchParams
in IE8- that was broken in the previous release__lookupGetter__
entriesChangelog
RegExp
flags handlingfetch
APIChangelog
Array
by copy proposal:
/actual/
entry points for methods from this proposalArray.prototype.toSpliced
throws a TypeError
instead of RangeError
if the result length is more than MAX_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 the Array
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.core-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
and core-js-compat
, now it's modules
and exclude
optionstargets
option of core-js-compat
means that the targets
filter just will not be applied, so the result will contain modules required for all possible engines.stack
property on DOMException
marked as supported from Deno 1.15Changelog
atob
btoa
Changelog
Function#bind
polyfills, uses only native Function#bind
in the internalsstructuredClone
should throw an error if no arguments passed__core-js_shared__
Changelog
Object.{ defineProperty, defineProperties }
bug, Babel issue%TypedArray%.prototype.set
bugs, affects modern engines (like Chrome < 95 or Safari < 14.1)Changelog
structuredClone
method from the HTML spec, see MDN
html/5749
DOMException
polyfill, the Web IDL spec, see MDN
DOMException
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 obsolete String#at
proposal module, #1019Array.prototype.{ values, @@iterator }.name
in V8 ~ Chrome 45-core-js/actual/**
namespaceChangelog
URLSearchParams
iterator .next
that should be enumerable by the specSubscription