Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
core-js-compat
Advanced tools
core-js-compat - npm Package Versions
Changelog
- Added a workaround of a Nashorn bug with
Function.prototype.{ call, apply, bind }on string methods, #1128 - Updated lists of
[Serializable]and[Transferable]objects in thestructuredClonepolyfill. Mainly, for better error messages if polyfilling of cloning such types is impossible Array.prototype.{ group, groupToMap }marked as supported from V8 ~ Chromium 108- Added Electron 22 compat data mapping
Changelog
- Forced polyfilling of
Array.prototype.groupToMapin the pure version for returning wrappedMapinstances - Fixed existence of
Array.prototype.{ findLast, findLastIndex }in/stage/4entry - Added Opera Android 71 compat data mapping
- Some stylistic changes
Changelog
- Considering
document.allas a callable in some missed cases - Added Safari 16.0 compat data
- Added iOS Safari 16.0 compat data mapping
- Fixed some ancient iOS Safari versions compat data mapping
Changelog
- Added some fixes and workarounds of FF30- typed arrays bug that does not properly convert objects to numbers
- Added
sideEffectsfield tocore-js-purepackage.jsonfor better tree shaking, #1117 - Dropped
semverdependency fromcore-js-compatsemverpackage (ironically) added a breaking change and dropped NodeJS 8 support in the minor7.1version, after thatsemverincore-js-compatwas pinned to7.0since for avoiding breaking changes it should support NodeJS 8. However, sincecore-js-compatis usually used with other packages that usesemverdependency, it causes multiple duplication ofsemverin dependencies. So I decided to removesemverdependency and replace it with a couple of simple helpers.
- Added Bun 0.1.6-0.1.11 compat data
- Added Deno 1.25 compat data mapping
- Updated Electron 21 compat data mapping
- Some stylistic changes, minor fixes, and improvements
Changelog
- Added
Object.prototype.__proto__polyfill- It's optional, legacy, and in some cases (mainly because of developers' mistakes) can cause problems, but some libraries depend on it, and most code can't work without the proper libraries' ecosystem
- Only for modern engines where this feature is missed (like Deno), it's not installed in IE10- since here we have no proper way setting of the prototype
- Without fixes of early implementations where it's not an accessor since those fixes are impossible
- Only for the global version
- Considering
document.allas an object in some missed cases, see ECMAScript Annex B 3.6 - Avoiding unnecessary promise creation and validation result in
%WrapForValid(Async)IteratorPrototype%.return, proposal-iterator-helpers/215 - Fixed omitting the result of proxing
.returnin%IteratorHelperPrototype%.return, #1116 - Fixed the order creation of properties of iteration result object of some iterators (
valueshould be created beforedone) - Fixed some cases of Safari < 13 bug - silent on non-writable array
.lengthsetting - Fixed
ArrayBuffer.lengthin V8 ~ Chrome 27- - Relaxed condition of re-usage native
WeakMapfor internal states with multiplecore-jscopies - Availability cloning of
FileListin thestructuredClonepolyfill extended to some more old engines versions - Some stylistic changes and minor fixes
- Throwing a
TypeErrorincore-js-compat/core-js-builderin case of passing invalid module names / filters for avoiding unexpected result, related to #1115 - Added missed NodeJS 13.2 to
esmodulescore-js-compat/core-js-buildertarget - Added Electron 21 compat data mapping
- Added Oculus Browser 23.0 compat data mapping
Changelog
- NodeJS is ignored in
IS_BROWSERdetection to avoid a false positive withjsdom, #1110 - Fixed detection of
@@speciessupport inPromisein some old engines { Array, %TypedArray% }.prototype.{ findLast, findLastIndex }marked as shipped in FF104- Added iOS Safari 15.6 compat data mapping
- Fixed Opera 15 compat data mapping
Changelog
- Recent updates of the iterator helpers proposal, #1101:
.asIndexedPairsrenamed to.indexed, proposal-iterator-helpers/183:Iterator.prototype.asIndexedPairs->Iterator.prototype.indexedAsyncIterator.prototype.asIndexedPairs->AsyncIterator.prototype.indexed
- Avoid exposing spec fiction
%AsyncFromSyncIteratorPrototype%inAsyncIterator.fromandIterator.prototype.toAsync, proposal-iterator-helpers/182, proposal-iterator-helpers/202 - Avoid unnecessary promise creation in
%WrapForValidAsyncIteratorPrototype%.next, proposal-iterator-helpers/197 - Do not validate value in
%WrapForValid(Async)IteratorPrototype%.next, proposal-iterator-helpers/197 and proposal-iterator-helpers/205 - Do not forward the parameter of
.next/.returnto an underlying iterator by the extended iterator protocol, a part of proposal-iterator-helpers/194 .throwmethods removed from all wrappers / helpers prototypes, a part of proposal-iterator-helpers/194- Close inner iterators of
{ Iterator, AsyncIterator }.prototype.flatMapproxy iterators on.return, proposal-iterator-helpers/195 - Throw
RangeErroronNaNin{ Iterator, AsyncIterator }.prototype.{ drop, take }, proposal-iterator-helpers/181 - Many other updates and fixes of this proposal
%TypedArray%.prototype.toSplicedmethod removed from the change array by copy proposal and marked as obsolete incore-js, proposal-change-array-by-copy/88- Polyfill
Promisewithunhandledrejectionevent support (browser style) in Deno < 1.24 - Available new targets in
core-js-compat/core-js-builderand added compat data for them: - Added Samsung Internet 18.0 compat data mapping
Changelog
- Added a workaround of the Bun ~ 0.1.1 bug that define some globals with incorrect property descriptors and that causes a crash of
core-js - Added a fix of the FF103+
structuredClonebugs (1774866 (fixed in FF104) and 1777321 (still not fixed)) that now can clone errors, but.stackof the clone is an empty string - Fixed
{ Map, WeakMap }.prototype.emplacelogic, #1102 - Fixed order of errors throwing on iterator helpers