This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade core-js from 3.23.4 to 3.30.2.
:information_source: 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.
- The recommended version is **20 versions** ahead of your current version.
- The recommended version was released **23 days ago**, on 2023-05-06.
Release notes Package name: core-js
ArrayBuffer.prototype.transfer (only in runtimes with native structuredClone with ArrayBuffer transfer support)
ArrayBuffer.prototype.transferToFixedLength (only in runtimes with native structuredClone with ArrayBuffer transfer support)
In backwards, in runtimes with native ArrayBuffer.prototype.transfer, but without proper structuredClone, added ArrayBuffer transfer support to structuredClone polyfill
Improved some cases handling of array-replacer in JSON.stringify symbols handling fix
Fixed many other old JSON.{ parse, stringify } bugs (numbers instead of strings as keys in replacer, handling negative zeroes, spaces, some more handling symbols cases, etc.)
Fixed configurability and ToString conversion of some accessors
Added throwing proper errors on an incorrect context in some ArrayBuffer and DataView methods
Some minor DataView and %TypedArray% polyfills optimizations
Added proper error on the excess number of trailing = in the atob polyfill
Fixed theoretically possible ReDoS vulnerabilities in String.prototype.{ trim, trimEnd, trimRight }, parse(Int|Float), Number, atob, and URL polyfills in some ancient engines
Compat data improvements:
RegExp.prototype.flags marked as fixed from V8 ~ Chrome 111
Disabled forced replacing of Array.fromAsync since it's on Stage 3
Avoiding a check of the target in the internal function-uncurry-this helper where it's not required - minor optimization and preventing problems in some broken environments, a workaround of #1141
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](https://app.snyk.io/org/blacklight/project/96bfd125-5816-4d9e-83c6-94d1569ab0f1?utm_source=github&utm_medium=referral&page=upgrade-pr)
🛠 [Adjust upgrade PR settings](https://app.snyk.io/org/blacklight/project/96bfd125-5816-4d9e-83c6-94d1569ab0f1/settings/integration?utm_source=github&utm_medium=referral&page=upgrade-pr)
🔕 [Ignore this dependency or unsubscribe from future upgrade PRs](https://app.snyk.io/org/blacklight/project/96bfd125-5816-4d9e-83c6-94d1569ab0f1/settings/integration?pkg=core-js&utm_source=github&utm_medium=referral&page=upgrade-pr#auto-dep-upgrades)
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade core-js from 3.23.4 to 3.30.2.
:information_source: 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.- The recommended version is **20 versions** ahead of your current version. - The recommended version was released **23 days ago**, on 2023-05-06.
Release notes
Package name: core-js
File
viastructuredClone
String
optimization, #1242URL.canParse
marked as supported (fixed) from NodeJS 20.1.0 and Deno 1.33.2URL.canParse
bugJSON.parse
source text access proposal features marked as supported from V8 ~ Chrome 114ArrayBuffer.prototype.transfer
and friends proposal features marked as supported from V8 ~ Chrome 114URLSearchParams.prototype.size
marked as supported from V8 ~ Chrome 113URL.canParse
method, url/763Set
methods proposal:Set.prototype.intersection
, March 2023 TC39 meeting, proposal-set-methods/94(Async)DisposableStack.prototype.move
marks the original stack as disposed, #1226Iterator.range
proposal:Symbol.metadata
, March 2023 TC39 meeting, proposal-decorator-metadata/12URLSearchParams.prototype.size
marked as supported from FF112, NodeJS 19.8 and Deno 1.32ToString
conversion / built-ins nature of some accessorsString.prototype.{ isWellFormed, toWellFormed }
marked as supported from V8 ~ Chrome 111URLSearchParams.prototype.size
getter, url/734ArrayBuffer
s in thestructuredClone
polyfill/(stable|actual|full)/instance/unshift
entries, #1207Set
methods proposal marked as supported from Bun 0.5.7String.prototype.toWellFormed
marked as fixed from Bun 0.5.7I highly recommend reading this: So, what's next?
Array
by copy proposal:Array.prototype.toReversed
Array.prototype.toSorted
Array.prototype.toSpliced
Array.prototype.with
%TypedArray%.prototype.toReversed
%TypedArray%.prototype.toSorted
%TypedArray%.prototype.with
es.
namespace modules,/es/
and/stable/
namespaces entriesJSON.parse
source text access Stage 3 proposalJSON.parse
patched for supportsource
inreviver
function argumentsJSON.rawJSON
JSON.isRawJSON
JSON.stringify
patched for supportJSON.rawJSON
ArrayBuffer.prototype.transfer
and friends Stage 3 proposal:ArrayBuffer.prototype.detached
ArrayBuffer.prototype.transfer
(only in runtimes with nativestructuredClone
withArrayBuffer
transfer support)ArrayBuffer.prototype.transferToFixedLength
(only in runtimes with nativestructuredClone
withArrayBuffer
transfer support)ArrayBuffer.prototype.transfer
, but without properstructuredClone
, addedArrayBuffer
transfer support tostructuredClone
polyfillAsyncIterator
helpers, proposal-iterator-helpers/262InstallErrorCause
removed fromSuppressedError
, January 2023 TC39 meeting, proposal-explicit-resource-management/145{ AsyncDisposableStack, DisposableStack }.prototype.use
, proposal-explicit-resource-management/143Symbol
predicates Stage 2 proposalSymbol.isRegistered
Symbol.isWellKnown
Number.range
Stage 1 proposal and method renamed toIterator.range
Function.prototype.unThis
Stage 0 proposal and method renamed toFunction.prototype.demethodize
String.prototype.toWellFormed
ToString
conversion bugJSON.stringify
symbols handling fixJSON.{ parse, stringify }
bugs (numbers instead of strings as keys in replacer, handling negative zeroes, spaces, some more handling symbols cases, etc.)ToString
conversion of some accessorsArrayBuffer
andDataView
methodsDataView
and%TypedArray%
polyfills optimizations=
in theatob
polyfillString.prototype.{ trim, trimEnd, trimRight }
,parse(Int|Float)
,Number
,atob
, andURL
polyfills in some ancient enginesRegExp.prototype.flags
marked as fixed from V8 ~ Chrome 111core-js-builder
Set
methods proposal updates:Set
-like objects on early exit, proposal-set-methods/85webpack
dev server bug on IE global methods, #1161String.{ raw, cooked }
error with empty template arrayError.captureStackTrace
instead of stack parsing in new error classes / wrappers where it's possiblePromise.{ allSettled, any }
feature detection, Hermes issueArray
by copy proposal marked as supported from V8 ~ Chrome 110self
marked as fixed in Deno 1.29.3, deno/17362core-js-bundle
WeakMap
keysString.dedent
in MS EdgeArray.fromAsync
since it's on Stage 3function-uncurry-this
helper where it's not required - minor optimization and preventing problems in some broken environments, a workaround of #1141Array.prototype.{ group, groupToMap }
in V8 ~ Chromium 108, proposal-array-grouping/44Commit messages
Package name: core-js
**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: