This repository has been archived by the owner on Mar 8, 2022. It is now read-only.
fix(deps): update dependency core-js to v3.21.1 #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
chore(deps): update dependency commitizen to v4.2.4
chore(deps): update dependency sass-loader to v11
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
2188b28
to
46ce0e0
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
46ce0e0
to
d0aeef8
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
d0aeef8
to
0538eec
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
0538eec
to
1083dd6
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
1083dd6
to
8b23225
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
8b23225
to
13648cb
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/core-js-3.x
branch
from
13648cb
to
c74091c
Compare
renovate
bot
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.12.1->3.21.1Release Notes
zloirock/core-js
v3.21.1Compare Source
Array.prototype.{ groupBy, groupByToMap }implementationcore-js-compattargets parser transforms engine names to lower caseatob/btoamarked as fixed in NodeJS 17.5v3.21.0Compare Source
atobbtoav3.20.3Compare Source
Function#bindpolyfills, uses only nativeFunction#bindin the internalsstructuredCloneshould throw an error if no arguments passed__core-js_shared__v3.20.2Compare Source
Object.{ defineProperty, defineProperties }bug, Babel issue%TypedArray%.prototype.setbugs, affects modern engines (like Chrome < 95 or Safari < 14.1)v3.20.1Compare Source
Promise.prototype.then, #1026v3.20.0Compare Source
structuredClonemethod from the HTML spec, see MDNhtml/5749DOMExceptionpolyfill, the Web IDL spec, see MDNDOMExceptionand its attributes polyfills with fixes of many different engines bugsDOMException#stackproperty polyfill in engines that should have itDOMExceptionimplementations where it's possible (for example, in old NodeJS where it's not exposed as global)causeon all Error typesError.prototype.toStringmethod polyfill with fixes of many different bugs of JS enginesNumber.prototype.toExponentialmethod polyfill with fixes of many different bugs of JS enginesArraygrouping proposal:Array.prototype.groupByToMapmethod@@​speciessupportArrayby copy stage 2 proposal:Array.prototype.toReversedArray.prototype.toSortedArray.prototype.toSplicedArray.prototype.with%TypedArray%.prototype.toReversed%TypedArray%.prototype.toSorted%TypedArray%.prototype.toSpliced%TypedArray%.prototype.withIterator.prototype.toAsyncmethod from the iterator helpers stage 2 proposalArray.fromAsyncproposal moved to stage 2String.cookedstage 1 proposal:Function.prototype.unThisstage 0 proposalFunction.{ isCallable, isConstructor }stage 0 proposal:Function.isCallableFunction.isConstructorString#atafter loading obsoleteString#atproposal module, #1019Array.prototype.{ values, @​@​iterator }.namein V8 ~ Chrome 45-core-js/actual/**namespacev3.19.3Compare Source
URLSearchParamsiterator.nextthat should be enumerable by the specSubscriptionv3.19.2Compare Source
RegExp#stickyflag, #1008, #1015Function#namepolyfill, #1010, thanks @ildar-shaimordanovArray.prototype[@​@​species]URLandURLSearchParamsv3.19.1Compare Source
ArrayBuffers are non-extensible, butObject.isExtensibledoes not report it:Object.{ isExtensible, isSealed, isFrozen }andReflect.isExtensibleArrayBuffers as collections keysObject#toStringonAggregateErrorin IE10-WeakMapin IE8-.findLastmethods family marked as supported from Chrome 97web.modulesv3.19.0Compare Source
core-jsfor preventing possible cases of breaking / observing the internal state by patching / deleting of them.call/.applyprototype methods that could be patchedinstanceofoperator - implicit.prototype/@@​hasInstanceaccess that could be patchedRegExp#test,String#matchand some over methods - implicit.execandRegExpwell-known symbols access that could be patchedErrorstack from extra entries experimentally added toAggregateError, #996, in case lack of problems it will be extended to other casesSymbolsupport, new well-known symbols created with usageSymbol.forfor ensuring the same keys in different realms, #998processpolyfill bug that incorrectly reports V8 version that's used in some cases ofcore-jsfeature detectionmessageAggregateErrorargumentMath.scale, a spec draft bugcore-js-builderwork in NodeJS 17, added a workaround ofwebpack+ NodeJS 17 issuev3.18.3Compare Source
AggregateErrorconstructor that should containErrorconstructorAggregateError.prototypeproperties descriptorsInstallErrorCauseinternal operationObject.hasOwnmarked as supported from Safari 15.1v3.18.2Compare Source
{ Array, %TypedArray% }.fromAsyncerrors moved to the promise, per the latest changes of the spec draftToInteger(OrInfinity)operation returns+0for-0argument, ES2020+ updateNumberconstructor wrapperString.rawwith extra argumentsv3.18.1Compare Source
String.prototype.substrfeature detection and compat data.forEachfrom prototypes of some DOM collections where it shouldn't be, #988, #987, thanks @moorejscausetoAggregateErrorconstructor implementation (still without adding to the feature detection).atand.findLastmethods marked as supported in Safari TPv3.18.0Compare Source
Array.fromAsyncstage 1 proposal:Array.fromAsync%TypedArray%.fromAsync.nameand.toString()on polyfilled functions improved in many different casesIsConstructorandIsCallablechecksGetMethodoperationparseInt/parseFloatwith boxed symbolses.array.{ index-of, last-index-of }compat datav3.17.3Compare Source
%IteratorPrototype%and%AsyncIteratorPrototype%in the futureDOMTokenList.prototype.{ forEach, @​@​iterator, keys, values, entries }in old WebKit versions whereelement.classListis not an instance of globalDOMTokenListv3.17.2Compare Source
v3.17.1Compare Source
modules-by-versionsdatav3.17.0Compare Source
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.v3.16.4Compare Source
AsyncFromSyncIteratormade stricter, related mainly toAsyncIterator.fromandAsyncIterator.prototype.flatMap.nextarguments in(Async)Iteratormethods is aligned with the current spec draft (mainly - ignoring the first passed to.nextargument in built-in generators).next,.return,.throwmethods onAsyncIteratorhelpers proxy iterators aligned with the current spec draft (built-in async generators) (mainly - some early errors moved to returned promises)v3.16.3Compare Source
CreateAsyncFromSyncIteratorsemantic inAsyncIterator.from, related to #765Object.prototype, #973v3.16.2Compare Source
Object.create(null)on WSH, #970v3.16.1Compare Source
v3.16.0Compare Source
Arrayfind from last proposal moved to the stage 3, July 2021 TC39 meetingArrayfiltering stage 1 proposal:Array.prototype.filterRejectreplacesArray.prototype.filterOut%TypedArray%.prototype.filterRejectreplaces%TypedArray%.prototype.filterOutArraygrouping stage 1 proposal:Array.prototype.groupBy%TypedArray%.prototype.groupBy@@​toPrimitivein some cases ofToPrimitiveinternal logic made stricterRequestwith polyfilledURLSearchParams, #965Object.create(null)on WSH, #966RegExp#execDate.prototype.getYearfeature detectiondenotarget incore-js-compat/core-js-builderObject.hasOwnmarked as supported from V8 9.3 and FF92Date.prototype.getYearmarked as not supported in IE8-summaryoption tocore-js-builder, see more info in theREADME, #910v3.15.2Compare Source
zone.jsloaded beforecore-js, #953v3.15.1Compare Source
RegExpconstructor, #948v3.15.0Compare Source
v3.14.0Compare Source
{ Array, %TypedArray% }.prototype.sort, #769, #941Safari14.0-%TypedArray%.prototype.sortvalidation of arguments bug.atmarked as supported from V8 9.2v3.13.1Compare Source
get-own-property-symbolsthird-partySymbolpolyfill if it's used since it causes a stack overflow, #774Object.prototypeaccessors methods in WebKit ~ Android 4.0, #232v3.13.0Compare Source
Object#hasOwnProperty(Object.hasOwn) proposal moved to the stage 3, May 2021 TC39 meetingConfiguration
📅 Schedule: 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.