build: update dependency core-js to v3
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| core-js | dependencies | major | ^2.5.4 -> ^3.0.0 |
β Dependency Lookup Warnings β
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
zloirock/core-js
v3.25.1
- 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-compat-
semverpackage (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
v3.25.0
- 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
v3.24.1
- 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
v3.24.0
- Recent updates of the iterator helpers proposal, #β1101:
-
.asIndexedPairsrenamed to.indexed, proposal-iterator-helpers/183:-
Iterator.prototype.asIndexedPairs->Iterator.prototype.indexed -
AsyncIterator.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
v3.23.5
- Fixed a typo in the
structuredClonefeature detection, #β1106 - Added Opera Android 70 compat data mapping
v3.23.4
- 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
v3.23.3
- Changed the order of operations in
%TypedArray%.prototype.toSplicedfollowing proposal-change-array-by-copy/89 - Fixed regression of some IE8- issues
v3.23.2
- Avoided creation of extra properties for the handling of
%TypedArray%constructors in new methods, #β1092 (comment) - Added Deno 1.23 compat data mapping
v3.23.1
- Fixed possible error on multiple
core-jscopies, #β1091 - Added
vflag toRegExp.prototype.flagsimplementation in case if current V8 bugs will not be fixed before this flag implementation
v3.23.0
-
Arrayfind 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
-
- Methods from the
Arraygrouping proposal renamed, according to June 2022 TC39 meeting:-
Array.prototype.groupBy->Array.prototype.group -
Array.prototype.groupByToMap->Array.prototype.groupToMap
-
- Changed the order of operations in
%TypedArray%.prototype.withfollowing proposal-change-array-by-copy/86, according to June 2022 TC39 meeting -
Decorator Metadata proposal extracted from Decorators proposal as a separate stage 2 proposal, according to March 2022 TC39 meeting,
Symbol.metadataKeyreplacesSymbol.metadata - Added
Array.prototype.pushpolyfill with some fixes for modern engines - Added
Array.prototype.unshiftpolyfill with some fixes for modern engines - Fixed a bug in the order of getting flags in
RegExp.prototype.flagsin the actual version of V8 - Fixed property descriptors of some
MathandNumberconstants - Added a workaround of V8
ArrayBufferDetachingprotector cell invalidation and performance degradation onstructuredClonefeature detection, one more case of #β679 - Added detection of NodeJS bug in
structuredClonethat can not cloneDOMException(just in case for future versions that will fix other issues) - Compat data:
- Added NodeJS 18.3 compat data mapping
- Added and fixed Deno 1.22 and 1.21 compat data mapping
- Added Opera Android 69 compat data mapping
- Updated Electron 20.0 compat data mapping
v3.22.8
- Fixed possible multiple call of
ToBigInt/ToNumberconversion of the argument passed to%TypedArray%.prototype.fillin V8 ~ Chrome < 59, Safari < 14.1, FF < 55, Edge <=18 - Fixed some cases of
DeletePropertyOrThrowin IE9- - Fixed the kind of error (
TypeErrorinstead ofError) on incorrectexecresult inRegExp.prototype.testpolyfill - Fixed dependencies of
{ actual, full, features }/typed-array/atentries - Added Electron 20.0 compat data mapping
- Added iOS Safari 15.5 compat data mapping
- Refactoring
v3.22.7
- Added a workaround for V8 ~ Chrome 53 bug with non-writable prototype of some methods, #β1083
v3.22.6
- Fixed possible double call of
ToNumberconversion on arguments ofMath.{ fround, trunc }polyfills -
Array.prototype.includesmarked as fixed in FF102
v3.22.5
- Ensured that polyfilled constructors
.prototypeis non-writable - Ensured that polyfilled methods
.prototypeis not defined - Added detection and fix of a V8 ~ Chrome <103 bug of
struturedClonethat returnsnullif cloned object contains multiple references to one error
v3.22.4
- Ensured proper
.lengthof polyfilled functions even in compressed code (excepting some ancient engines) - Ensured proper
.nameof polyfilled accessors (excepting some ancient engines) - Ensured proper source /
ToStringconversion of polyfilled accessors - Actualized Rhino compat data
- Refactoring
v3.22.3
- Added a fix for FF99+
Array.prototype.includesbroken on sparse arrays
v3.22.2
- Fixed
URLSearchParamsin IE8- that was broken in the previous release - Fixed
__lookupGetter__entries
v3.22.1
- Improved some cases of
RegExpflags handling - Prevented experimental warning in NodeJS ~ 18.0 on detection
fetchAPI - Added NodeJS 18.0 compat data
v3.22.0
-
Change
Arrayby copy proposal:- Moved to Stage 3, March TC39 meeting
- Disabled forced replacement and added
/actual/entry points for methods from this proposal -
Array.prototype.toSplicedthrows aTypeErrorinstead ofRangeErrorif the result length is more thanMAX_SAFE_INTEGER, proposal-change-array-by-copy/70
- Added some more
atob/btoafixes:- NodeJS <17.9
atobdoes not ignore spaces, node/42530 - Actual NodeJS
atobdoes not validate encoding, node/42646 - FF26- implementation does not properly convert argument to string
- IE / Edge <16 implementation have wrong arity
- NodeJS <17.9
- Added
/full/namespace as the replacement for/features/since it's more descriptive in context of the rest namespaces (/es/β/stable/β/actual/β/full/) - Avoided propagation of removed parts of proposals to upper stages. For example,
%TypedArray%.prototype.groupBywas removed from theArraygrouping 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. - Significant internal refactoring and splitting of modules (but without exposing to public API since it will be a breaking change - it will be exposed in the next major version)
- Bug fixes:
- Tooling:
- Stabilized proposals are filtered out from the
core-js-compat->core-js-builder->core-js-bundleoutput. 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. - Aligned modules filters of
core-js-builderandcore-js-compat, now it'smodulesandexcludeoptions - Added support of entry points, modules, regexes, and arrays of them to those filters
- Missed
targetsoption ofcore-js-compatmeans that thetargetsfilter just will not be applied, so the result will contain modules required for all possible engines
- Stabilized proposals are filtered out from the
- Compat data:
-
.stackproperty onDOMExceptionmarked as supported from Deno 1.15 - Added Deno 1.21 compat data mapping
- Added Electron 19.0 and updated 18.0 compat data mapping
- Added Samsung Internet 17.0 compat data mapping
- Added Opera Android 68 compat data mapping
-
v3.21.1
- Added a bugfix for the WebKit
Array.prototype.{ groupBy, groupByToMap }implementation -
core-js-compattargets parser transforms engine names to lower case -
atob/btoamarked as fixed in NodeJS 17.5 - Added Electron 18.0 compat data mapping
- Added Deno 1.20 compat data mapping
v3.21.0
- Added Base64 utility methods:
-
atob -
btoa
-
- Added the proper validation of arguments to some methods from web standards
- Forced replacement of all features from early-stage proposals for avoiding possible web compatibility issues in the future
- Added Rhino 1.7.14 compat data
- Added Deno 1.19 compat data mapping
- Added Opera Android 66 and 67 compat data mapping
- Added iOS Safari 15.3 and 15.4 compat data mapping
v3.20.3
- Detects and replaces broken third-party
Function#bindpolyfills, uses only nativeFunction#bindin the internals -
structuredCloneshould throw an error if no arguments passed - Changed the structure of notes in
__core-js_shared__
v3.20.2
- Added a fix of a V8 ~ Chrome 36-
Object.{ defineProperty, defineProperties }bug, Babel issue - Added fixes of some different
%TypedArray%.prototype.setbugs, affects modern engines (like Chrome < 95 or Safari < 14.1)
v3.20.1
- Fixed the order of calling reactions of already fulfilled / rejected promises in
Promise.prototype.then, #β1026 - Fixed possible memory leak in specific promise chains
- Fixed some missed dependencies of entries
- Added Deno 1.18 compat data mapping
v3.20.0
- Added
structuredClonemethod from the HTML spec, see MDN- Includes all cases of cloning and transferring of required ECMAScript and platform types that can be polyfilled, for the details see the caveats
- Uses native structured cloning algorithm implementations where it's possible
- Includes the new semantic of errors cloning from
html/5749
- Added
DOMExceptionpolyfill, the Web IDL spec, see MDN- Includes
DOMExceptionand its attributes polyfills with fixes of many different engines bugs - Includes
DOMException#stackproperty polyfill in engines that should have it - Reuses native
DOMExceptionimplementations where it's possible (for example, in old NodeJS where it's not exposed as global)
- Includes
- Added support of
causeon all Error types - Added
Error.prototype.toStringmethod polyfill with fixes of many different bugs of JS engines - Added
Number.prototype.toExponentialmethod polyfill with fixes of many different bugs of JS engines -
Arraygrouping proposal:- Moved to stage 3
- Added
Array.prototype.groupByToMapmethod - Removed
@@​speciessupport
- Added change
Arrayby 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
-
- Added
Iterator.prototype.toAsyncmethod from the iterator helpers stage 2 proposal -
Array.fromAsyncproposal moved to stage 2 - Added
String.cookedstage 1 proposal: - Added
Function.prototype.unThisstage 0 proposal - Added
Function.{ isCallable, isConstructor }stage 0 proposal:-
Function.isCallable -
Function.isConstructor
-
- Added a workaround of most cases breakage modern
String#atafter loading obsoleteString#atproposal module, #β1019 - Fixed
Array.prototype.{ values, @​@​iterator }.namein V8 ~ Chrome 45- - Fixed validation of typed arrays in typed arrays iteration methods in V8 ~ Chrome 50-
- Extension of the API, #β1012
- Added a new
core-js/actual/**namespace - Added entry points for each finished post-ES6 proposal
- Added a new
v3.19.3
- Fixed internal slots check in methods of some built-in types, #β1017
- Fixed
URLSearchParamsiterator.nextthat should be enumerable by the spec - Refactored
Subscription - Added NodeJS 17.2 compat data mapping
v3.19.2
- Added a workaround for a UC Browser specific version bug with unobservable
RegExp#stickyflag, #β1008, #β1015 - Added handling of comments and specific spaces to
Function#namepolyfill, #β1010, thanks @βildar-shaimordanov - Prevented some theoretical cases of breaking / observing the internal state by patching
Array.prototype[@​@​species] - Refactored
URLandURLSearchParams - Added iOS Safari 15.2 compat data mapping
- Added Electron 17.0 compat data mapping
- Updated Deno compat data mapping
v3.19.1
- Added a workaround for FF26- bug where
ArrayBuffers are non-extensible, butObject.isExtensibledoes not report it:- Fixed in
Object.{ isExtensible, isSealed, isFrozen }andReflect.isExtensible - Fixed handling of
ArrayBuffers as collections keys
- Fixed in
- Fixed
Object#toStringonAggregateErrorin IE10- - Fixed possible lack of dependencies of
WeakMapin IE8- -
.findLastmethods family marked as supported from Chrome 97 - Fixed inheritance of Electron compat data
web.modules - Fixed Safari 15.1 compat data (some features were not added)
- Added iOS Safari 15.1 compat data mapping
v3.19.0
- Most built-ins are encapsulated in
core-jsfor preventing possible cases of breaking / observing the internal state by patching / deleting of them- Avoid
.call/.applyprototype methods that could be patched - Avoid
instanceofoperator - implicit.prototype/@@​hasInstanceaccess that could be patched - Avoid
RegExp#test,String#matchand some over methods - implicit.execandRegExpwell-known symbols access that could be patched
- Avoid
- Clearing of
Errorstack from extra entries experimentally added toAggregateError, #β996, in case lack of problems it will be extended to other cases - In engines with native
Symbolsupport, new well-known symbols created with usageSymbol.forfor ensuring the same keys in different realms, #β998 - Added a workaround of a BrowserFS NodeJS
processpolyfill bug that incorrectly reports V8 version that's used in some cases ofcore-jsfeature detection - Fixed normalization of
messageAggregateErrorargument - Fixed order of arguments conversion in
Math.scale, a spec draft bug - Fixed
core-js-builderwork in NodeJS 17, added a workaround ofwebpack+ NodeJS 17 issue - Added NodeJS 17.0 compat data mapping
- Added Opera Android 65 compat data mapping
- Updated Electron 16.0 compat data mapping
- Many other minor fixes and improvements
v3.18.3
- Fixed the prototype chain of
AggregateErrorconstructor that should containErrorconstructor - Fixed incorrect
AggregateError.prototypeproperties descriptors - Fixed
InstallErrorCauseinternal operation - Added NodeJS 16.11 compat data mapping
- Added Deno 1.16 compat data mapping
-
Object.hasOwnmarked as supported from Safari 15.1
v3.18.2
- Early
{ Array, %TypedArray% }.fromAsyncerrors moved to the promise, per the latest changes of the spec draft - Internal
ToInteger(OrInfinity)operation returns+0for-0argument, ES2020+ update - Fixed theoretical problems with handling bigint in
Numberconstructor wrapper - Fixed
String.rawwith extra arguments - Fixed some missed dependencies in entry points
- Some other minor fixes and improvements
- Refactoring
v3.18.1
- Fixed
String.prototype.substrfeature detection and compat data - Removed mistakenly added
.forEachfrom prototypes of some DOM collections where it shouldn't be, #β988, #β987, thanks @βmoorejs - Added
causetoAggregateErrorconstructor implementation (still without adding to the feature detection) - Families of
.atand.findLastmethods marked as supported in Safari TP - Added Electron 16.0 compat data mapping
v3.18.0
- Added
Array.fromAsyncstage 1 proposal:-
Array.fromAsync -
%TypedArray%.fromAsync
-
-
.nameand.toString()on polyfilled functions improved in many different cases - Improved internal
IsConstructorandIsCallablechecks - Fixed some internal cases of
GetMethodoperation - Fixed a bug of MS Edge 18-
parseInt/parseFloatwith boxed symbols - Fixed
es.array.{ index-of, last-index-of }compat data - Added Deno 1.15 compat data mapping
- Some other minor fixes and optimizations
v3.17.3
- Fixed some possible problems related to possible extension of
%IteratorPrototype%and%AsyncIteratorPrototype%in the future - Fixed
DOMTokenList.prototype.{ forEach, @​@​iterator, keys, values, entries }in old WebKit versions whereelement.classListis not an instance of globalDOMTokenList - Added NodeJS 16.9 compat data mapping
- Added Samsung Internet 16.0 compat data mapping
v3.17.2
- Fixed missed cases of ES3 reserved words usage, related to #β980
- Fixed dependencies in one missed entry point
- Some other minor fixes and optimizations
v3.17.1
- Fixed missed
modules-by-versionsdata
v3.17.0
-
Accessible
Object.prototype.hasOwnProperty(Object.hasOwn) proposal moved to the stable ES, per August 2021 TC39 meeting -
Relative indexing method (
.at) proposal moved to the stable ES, per August 2021 TC39 meeting - Exposed by default the stable version of
String.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. - Some more iteration closing fixes
- Fixed an ES3 reserved words usage, #β980
v3.16.4
-
AsyncFromSyncIteratormade stricter, related mainly toAsyncIterator.fromandAsyncIterator.prototype.flatMap - Handling of optional
.nextarguments in(Async)Iteratormethods is aligned with the current spec draft (mainly - ignoring the first passed to.nextargument in built-in generators) - Behavior of
.next,.return,.throwmethods onAsyncIteratorhelpers proxy iterators aligned with the current spec draft (built-in async generators) (mainly - some early errors moved to returned promises) - Fixed some cases of safe iteration closing
- Fixed dependencies of some entry points
v3.16.3
- Fixed
CreateAsyncFromSyncIteratorsemantic inAsyncIterator.from, related to #β765 - Added a workaround of a specific case of broken
Object.prototype, #β973
v3.16.2
- Added a workaround of a Closure Compiler unsafe optimization, #β972
- One more fix crashing of
Object.create(null)on WSH, #β970 - Added Deno 1.14 compat data mapping
v3.16.1
- Fixed microtask implementation on iOS Pebble, #β967
- Fixed some entry points
- Improved old Safari compat data
v3.16.0
-
Arrayfind from last proposal moved to the stage 3, July 2021 TC39 meeting -
Arrayfiltering stage 1 proposal:-
Array.prototype.filterRejectreplacesArray.prototype.filterOut -
%TypedArray%.prototype.filterRejectreplaces%TypedArray%.prototype.filterOut
-
- Added
Arraygrouping stage 1 proposal:-
Array.prototype.groupBy -
%TypedArray%.prototype.groupBy
-
- Work with symbols made stricter: some missed before cases of methods that should throw an error on symbols now works as they should
- Handling
@@​toPrimitivein some cases ofToPrimitiveinternal logic made stricter - Fixed work of
Requestwith polyfilledURLSearchParams, #β965 - Fixed possible exposing of collections elements metadata in some cases, #β427
- Fixed crashing of
Object.create(null)on WSH, #β966 - Fixed some cases of typed arrays subclassing logic
- Fixed a minor bug related to string conversion in
RegExp#exec - Fixed
Date.prototype.getYearfeature detection - Fixed content of some entry points
- Some minor optimizations and refactoring
- Deno:
- Added Deno support (sure, after bundling since Deno does not support CommonJS)
- Allowed
denotarget incore-js-compat/core-js-builder - A bundle for Deno published on deno.land/x/corejs
- Added / updated compat data / mapping:
- Added
summaryoption tocore-js-builder, see more info in theREADME, #β910
v3.15.2
- Worked around breakage related to
zone.jsloaded beforecore-js, #β953 - Added NodeJS 16.4 -> Chrome 91 compat data mapping
v3.15.1
- Fixed cloning of regex through
RegExpconstructor, #β948
v3.15.0
- Added
RegExpnamed capture groups polyfill, #β521, #β944 - Added
RegExpdotAllflag polyfill, #β792, #β944 - Added missed polyfills of Annex B features (required mainly for some non-browser engines), #β336, #β945:
-
escape -
unescape -
String.prototype.substr -
Date.prototype.getYear -
Date.prototype.setYear -
Date.prototype.toGMTString
-
- Fixed detection of forbidden host code points in
URLpolyfill - Allowed
rhinotarget incore-js-compat/core-js-builder, added compat data forrhino1.7.13, #β942, thanks @βgausie -
.atmarked as supported from FF90
v3.14.0
- Added polyfill of stable sort in
{ Array, %TypedArray% }.prototype.sort, #β769, #β941 - Fixed
Safari14.0-%TypedArray%.prototype.sortvalidation of arguments bug -
.atmarked as supported from V8 9.2
v3.13.1
- Overwrites
get-own-property-symbolsthird-partySymbolpolyfill if it's used since it causes a stack overflow, #β774 - Added a workaround of possible browser crash on
Object.prototypeaccessors methods in WebKit ~ Android 4.0, #β232
v3.13.0
- Accessible
Object#hasOwnProperty(Object.hasOwn) proposal moved to the stage 3, May 2021 TC39 meeting
v3.12.1
- Fixed some cases of
Function#toStringwith multiplecore-jsinstances - Fixed some possible
String#splitpolyfill problems in V8 5.1
v3.12.0
- Added well-known symbol
Symbol.metadatafor decorators stage 2 proposal - Added well-known symbol
Symbol.matcherfor pattern matching stage 1 proposal - Fixed regression of V8 ~ Node 0.12
String(Symbol())bug, #β933
v3.11.3
- Native promise-based APIs
Promise#{ catch, finally }returns polyfilledPromiseinstances when it's required
v3.11.2
- Added a workaround of WebKit ~ iOS 10.3 Safari
Promisebug, #β932 -
Promise#thenof incorrect nativePromiseimplementations with correct subclassing no longer wrapped - Changed the order of
Promisefeature detection, removed unhandled rejection tracking check in non-browser non-node platforms
v3.11.1
- Made
instanceof Promiseand.constructor === Promisework with polyfilledPromisefor all native promise-based APIs - Added a workaround for some buggy V8 versions ~4.5 related to fixing of
%TypedArray%static methods, #β564
v3.11.0
- Added accessible
Object#hasOwnPropertystage 2 proposal-
Object.hasOwnmethod
-
- Fixed a possible
RegExpconstructor problem with multiple globalcore-jsinstances
v3.10.2
-
URLandURLSearchParamsmarked as supported from Safari 14.0 - Polyfilled built-in constructors protected from calling on instances
v3.10.1
- Prevented possible
RegExp#splitproblems in old engines, #β751, #β919 - Detection of Safari 10 string padding bug extended to some Safari-based browsers
v3.10.0
-
Arrayfind from last proposal moved to the stage 2, March TC39 meeting - Prevented possible
RegExp#execproblems in some old engines, #β920 - Updated compat data mapping:
- NodeJS up to 16.0
- Electron up to 13.0
- Samsung Internet up to 14.0
- Opera Android up to 62
- The rest automatically
v3.9.1
- Added a workaround for Chrome 38-40 bug which does not allow to inherit symbols (incl. well-known) from DOM collections prototypes to instances, #β37
- Used
NumericRangeIteratoras toStringTag instead ofRangeIteratorin{ Number, BigInt }.rangeiterator, per this PR - TypedArray constructors marked as supported from Safari 14.0
- Updated compat data mapping for iOS Safari and Opera for Android
v3.9.0
- Added
Arrayfind from last stage 1 proposal-
Array#findLast -
Array#findLastIndex -
%TypedArray%#findLast -
%TypedArray%#findLastIndex
-
- Added
%TypedArray%#uniqueBymethod for array deduplication stage 1 proposal-
%TypedArray%#uniqueBy
-
- Dropped
ToLengthdetection from array methods feature detection which could cause hanging FF11-21 and some versions of old WebKit, #β764 - Minified bundle from
core-js-bundleusesterserinstead ofuglify-js
v3.8.3
- Fixed some more issues related to FF44- legacy
Iterator, #β906
v3.8.2
- Fixed handling of special replacements patterns in
String#replaceAll, #β900 - Fixed iterators dependencies of
Promise.anyandPromise.allSettledentries - Fixed microtask implementation on WebOS, #β898, #β901
v3.8.1
- Fixed work of new
%TypedArray%methods onBigIntarrays - Added ESNext methods to ES3 workaround for
Numberconstructor wrapper
v3.8.0
- Added relative indexing method stage 3 proposal
-
Array#at -
%TypedArray%#at
-
- Added
Number.rangestage 1 proposal-
Number.range -
BigInt.range
-
- Added array filtering stage 1 proposal
-
Array#filterOut -
%TypedArray%#filterOut
-
- Added array deduplication stage 1 proposal
-
Array#uniqueBy
-
- Added code points / code units explicit feature detection in
String#atfor preventing breakage code which use obsoleteString#atproposal polyfill - Added the missed
(es|stable)/instance/replace-allentries - Updated compat data mapping for Opera - from Opera 69, the difference with Chrome versions increased to 14
- Compat data mapping for modern Android WebView to Chrome moved from targets parser directly to compat data
- Deprecate
core-js-builderblacklistoption in favor ofexclude
v3.7.0
-
String#replaceAllmoved to the stable ES, per June TC39 meeting -
Promise.anyandAggregateErrormoved to the stable ES, per July TC39 meeting - Added
Reflect[@​@​toStringTag], per July TC39 meeting - Forced replacement of
Array#{ reduce, reduceRight }in Chrome 80-82 because of a bug, #β766 - Following the changes in the
upsertproposal,{ Map, WeakMap }#emplacereplace{ Map, WeakMap }#upsert, these obsolete methods will be removed in the next major release -
By the current spec,
AggregateError#errorsis own data property - Added correct iteration closing in the iteration helpers according to the current version of the proposal
-
process.nextTickhave a less priority thanPromisein the microtask implementation, #β855 - Fixed microtask implementation in engines with
MutationObserver, but withoutdocument, #β865, #β866 - Fixed
core-js-builderwith an empty (after the targets engines or another filtration) modules list, #β822 - Fixed possible twice call of
window.onunhandledrejection, #β760 - Fixed some possible problems related multiple global copies of
core-js, #β880 - Added a workaround for 3rd party
Reflect.setpolyfill bug, #β847 - Updated compat data:
- Chrome up to 86
- FF up to 82
- Safari up to 14
- Updated compat data mapping:
- iOS up to 14
- NodeJS up to 15.0
- Electron up to 11.0
- Samsung Internet up to 13.0
- Opera Android up to 60
- The rest automatically
- Updated all required dependencies
v3.6.5
- Updated Browserslist #β755
- Fixed
setImmediatein Safari #β770, thanks @βdtinth - Fixed some regexp, thanks @βscottarc
- Added OPEN_SOURCE_CONTRIBUTOR detection in
postinstall, thanks @βscottarc - Added Drone CI in
postinstallCI detection #β781
v3.6.4
- Prevented a possible almost infinite loop in non-standard implementations of some backward iteration array methods
v3.6.3
- Fixed replacement of substitutes of undefined capture groups in
.replacein Safari 13.0-, #β471, #β745, thanks @βmattclough1 - Improved compat data for old engines
v3.6.2
- Fixed early implementations of `Array#{
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.
- [ ] If you want to rebase/retry this PR, click this checkbox.
This PR has been generated by Renovate Bot.
@josephperrott @devversion do we generate these PRs using our tooling? It looks like the lint check is not happy about the commit message.
@AndrewKushnir This will be corrected by: https://github.com/angular/angular/pull/46611
@AndrewKushnir Yes, I created a PR for this: #46611 (Edit: we responded at the same time π -- no delay!)
Thanks Joey and Paul! π
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.