eslint-plugin-flowtype-errors
eslint-plugin-flowtype-errors copied to clipboard
fix(deps): update dependency core-js to v3.21.1
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| core-js | 3.8.1 -> 3.21.1 |
Release Notes
zloirock/core-js
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
Configuration
📅 Schedule: "before 3am on the first day of the month" (UTC).
🚦 Automerge: Disabled due to failing status checks.
♻ 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 WhiteSource Renovate. View repository job log here.