[Snyk] Upgrade core-js from 3.21.0 to 3.30.2 #12
Conversation
This file contains hidden or 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
Snyk has created this PR to upgrade core-js from 3.21.0 to 3.30.2. See this package in npm: https://www.npmjs.com/package/core-js See this project in Snyk: https://app.snyk.io/org/joneszachariahnoel/project/ce9be985-0a56-43b0-9d6c-df8ef2cc8e1a?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.21.0 to 3.30.2.
ℹ️ 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
-
3.30.2 - 2023-05-06
- Added a fix for a NodeJS 20.0.0 bug with cloning
- Added protection from Terser unsafe
- Added a workaround for getting proper global object in Figma plugins, #1231
- Compat data improvements:
- Added NodeJS 20.0 compat data mapping
- Added Deno 1.33 compat data mapping
-
3.30.1 - 2023-04-13
- Added a fix for a NodeJS 19.9.0
- Compat data improvements:
-
3.30.0 - 2023-04-03
- Added
- Removed sort from
- Iterator Helpers proposals (sync, async):
- Validate arguments before opening iterator, March 2023 TC39 meeting, proposal-iterator-helpers/265
- Explicit Resource Management proposals (sync, async):
- Some simplifications like proposal-explicit-resource-management/150
- Moved to Stage 2, March 2023 TC39 meeting
- Decorator Metadata proposal:
- Returned to usage
- Compat data improvements:
- Added Safari 16.4 compat data
- Added Deno 1.32 compat data mapping
- Added Electron 25 and updated 24 compat data mapping
- Added Samsung Internet 21 compat data mapping
- Added Quest Browser 26 compat data mapping
- Updated Opera Android 74 compat data
-
3.29.1 - 2023-03-13
- Fixed dependencies of some entries
- Fixed
- Added Opera Android 74 compat data mapping
-
3.29.0 - 2023-02-26
- Added
- Allowed cloning resizable
- Fixed wrong export in
- Compat data improvements:
- Added Deno 1.31 compat data mapping
-
3.28.0 - 2023-02-13
- Change
- Methods:
- Moved to stable ES, January 2023 TC39 meeting
- Added
- Added
- Methods:
- Added
- Built-ins:
- In backwards, in runtimes with native
- Iterator Helpers proposal:
- Splitted into 2 (sync and async) proposals, async version moved back to Stage 2, January 2023 TC39 meeting
- Allowed interleaved mapping in
- Explicit Resource Management Stage 3 and Async Explicit Resource Management Stage 2 proposals:
- Simplified internal behaviour of
- Added
- Methods:
- Fixed Safari
- Improved some cases handling of array-replacer in
- Fixed many other old
- Fixed configurability and
- Added throwing proper errors on an incorrect context in some
- Some minor
- Added proper error on the excess number of trailing
- Fixed theoretically possible ReDoS vulnerabilities in
- Compat data improvements:
- Added Opera Android 73 compat data mapping
- Added TypeScript definitions to
-
3.27.2 - 2023-01-18
- Closing of iterators of
- Some other minor internal changes
- Added one more workaround of a
- Fixed possible
- Used non-standard V8
- Added detection correctness of iteration to
- Compat data improvements:
- Change
- Added Samsung Internet 20 compat data mapping
- Added Quest Browser 25 compat data mapping
- Added React Native 0.71 Hermes compat data
- Added Electron 23 and 24 compat data mapping
- Minor tweaks of minification settings for
- Refactoring, some minor fixes, improvements, optimizations
-
3.27.1 - 2022-12-29
- Fixed a Chakra-based MS Edge (18-) bug that unfreeze (O_o) frozen arrays used as
- Fixing of the previous bug also fixes some cases of
- Fixed dependencies of some entries
-
3.27.0 - 2022-12-25
-
3.26.1 - 2022-11-13
- Disabled forced replacing of
- Avoiding a check of the target in the internal
- V8 will not ship
-
3.26.0 - 2022-10-23
-
3.25.5 - 2022-10-03
-
3.25.4 - 2022-10-02
-
3.25.3 - 2022-09-25
-
3.25.2 - 2022-09-18
-
3.25.1 - 2022-09-07
-
3.25.0 - 2022-08-24
-
3.24.1 - 2022-07-29
-
3.24.0 - 2022-07-25
-
3.23.5 - 2022-07-17
-
3.23.4 - 2022-07-09
-
3.23.3 - 2022-06-25
-
3.23.2 - 2022-06-20
-
3.23.1 - 2022-06-14
-
3.23.0 - 2022-06-13
-
3.22.8 - 2022-06-01
-
3.22.7 - 2022-05-24
-
3.22.6 - 2022-05-22
-
3.22.5 - 2022-05-10
-
3.22.4 - 2022-05-02
-
3.22.3 - 2022-04-28
-
3.22.2 - 2022-04-21
-
3.22.1 - 2022-04-19
-
3.22.0 - 2022-04-15
-
3.21.1 - 2022-02-16
-
3.21.0 - 2022-02-01
from core-js GitHub release notesFileviastructuredCloneStringoptimization, #1242URL.canParsemarked as supported (fixed) from NodeJS 20.1.0 and Deno 1.33.2URL.canParsebugJSON.parsesource text access proposal features marked as supported from V8 ~ Chrome 114ArrayBuffer.prototype.transferand friends proposal features marked as supported from V8 ~ Chrome 114URLSearchParams.prototype.sizemarked as supported from V8 ~ Chrome 113URL.canParsemethod, url/763Setmethods proposal:Set.prototype.intersection, March 2023 TC39 meeting, proposal-set-methods/94(Async)DisposableStack.prototype.movemarks the original stack as disposed, #1226Iterator.rangeproposal:Symbol.metadata, March 2023 TC39 meeting, proposal-decorator-metadata/12URLSearchParams.prototype.sizemarked as supported from FF112, NodeJS 19.8 and Deno 1.32ToStringconversion / built-ins nature of some accessorsString.prototype.{ isWellFormed, toWellFormed }marked as supported from V8 ~ Chrome 111URLSearchParams.prototype.sizegetter, url/734ArrayBuffers in thestructuredClonepolyfill/(stable|actual|full)/instance/unshiftentries, #1207Setmethods proposal marked as supported from Bun 0.5.7String.prototype.toWellFormedmarked as fixed from Bun 0.5.7I highly recommend reading this: So, what's next?
Arrayby copy proposal:Array.prototype.toReversedArray.prototype.toSortedArray.prototype.toSplicedArray.prototype.with%TypedArray%.prototype.toReversed%TypedArray%.prototype.toSorted%TypedArray%.prototype.withes.namespace modules,/es/and/stable/namespaces entriesJSON.parsesource text access Stage 3 proposalJSON.parsepatched for supportsourceinreviverfunction argumentsJSON.rawJSONJSON.isRawJSONJSON.stringifypatched for supportJSON.rawJSONArrayBuffer.prototype.transferand friends Stage 3 proposal:ArrayBuffer.prototype.detachedArrayBuffer.prototype.transfer(only in runtimes with nativestructuredClonewithArrayBuffertransfer support)ArrayBuffer.prototype.transferToFixedLength(only in runtimes with nativestructuredClonewithArrayBuffertransfer support)ArrayBuffer.prototype.transfer, but without properstructuredClone, addedArrayBuffertransfer support tostructuredClonepolyfillAsyncIteratorhelpers, proposal-iterator-helpers/262InstallErrorCauseremoved fromSuppressedError, January 2023 TC39 meeting, proposal-explicit-resource-management/145{ AsyncDisposableStack, DisposableStack }.prototype.use, proposal-explicit-resource-management/143Symbolpredicates Stage 2 proposalSymbol.isRegisteredSymbol.isWellKnownNumber.rangeStage 1 proposal and method renamed toIterator.rangeFunction.prototype.unThisStage 0 proposal and method renamed toFunction.prototype.demethodizeString.prototype.toWellFormedToStringconversion bugJSON.stringifysymbols handling fixJSON.{ parse, stringify }bugs (numbers instead of strings as keys in replacer, handling negative zeroes, spaces, some more handling symbols cases, etc.)ToStringconversion of some accessorsArrayBufferandDataViewmethodsDataViewand%TypedArray%polyfills optimizations=in theatobpolyfillString.prototype.{ trim, trimEnd, trimRight },parse(Int|Float),Number,atob, andURLpolyfills in some ancient enginesRegExp.prototype.flagsmarked as fixed from V8 ~ Chrome 111core-js-builderSetmethods proposal updates:Set-like objects on early exit, proposal-set-methods/85webpackdev server bug on IE global methods, #1161String.{ raw, cooked }error with empty template arrayError.captureStackTraceinstead of stack parsing in new error classes / wrappers where it's possiblePromise.{ allSettled, any }feature detection, Hermes issueArrayby copy proposal marked as supported from V8 ~ Chrome 110selfmarked as fixed in Deno 1.29.3, deno/17362core-js-bundleWeakMapkeysString.dedentin MS EdgeRead more
Array.fromAsyncsince it's on Stage 3function-uncurry-thishelper 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
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