[Snyk] Upgrade core-js from 3.9.0 to 3.21.1 #1
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.
Snyk has created this PR to upgrade core-js from 3.9.0 to 3.21.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: core-js
Array.prototype.{ groupBy, groupByToMap }
implementationcore-js-compat
targets parser transforms engine names to lower caseatob
/btoa
marked as fixed in NodeJS 17.5atob
btoa
Function#bind
polyfills, uses only nativeFunction#bind
in the internalsstructuredClone
should throw an error if no arguments passed__core-js_shared__
Object.{ defineProperty, defineProperties }
bug, Babel issue%TypedArray%.prototype.set
bugs, affects modern engines (like Chrome < 95 or Safari < 14.1)Promise.prototype.then
, #1026structuredClone
method from the HTML spec, see MDNhtml/5749
DOMException
polyfill, the Web IDL spec, see MDNDOMException
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 proposal:Function.prototype.unThis
stage 0 proposalFunction.{ isCallable, isConstructor }
stage 0 proposal:Function.isCallable
Function.isConstructor
String#at
after loading obsoleteString#at
proposal module, #1019Array.prototype.{ values, @@ iterator }.name
in V8 ~ Chrome 45-core-js/actual/**
namespaceURLSearchParams
iterator.next
that should be enumerable by the specSubscription
RegExp#sticky
flag, #1008, #1015Function#name
polyfill, #1010, thanks @ ildar-shaimordanovArray.prototype[@@ species]
URL
andURLSearchParams
ArrayBuffer
s are non-extensible, butObject.isExtensible
does not report it:Object.{ isExtensible, isSealed, isFrozen }
andReflect.isExtensible
ArrayBuffer
s as collections keysObject#toString
onAggregateError
in IE10-WeakMap
in IE8-.findLast
methods family marked as supported from Chrome 97web.
modulescore-js
for preventing possible cases of breaking / observing the internal state by patching / deleting of them.call
/.apply
prototype methods that could be patchedinstanceof
operator - implicit.prototype
/@@ hasInstance
access that could be patchedRegExp#test
,String#match
and some over methods - implicit.exec
andRegExp
well-known symbols access that could be patchedError
stack from extra entries experimentally added toAggregateError
, #996, in case lack of problems it will be extended to other casesSymbol
support, new well-known symbols created with usageSymbol.for
for ensuring the same keys in different realms, #998process
polyfill bug that incorrectly reports V8 version that's used in some cases ofcore-js
feature detectionmessage
AggregateError
argumentMath.scale
, a spec draft bugcore-js-builder
work in NodeJS 17, added a workaround ofwebpack
+ NodeJS 17 issueCommit messages
Package name: core-js
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs