[Snyk] Upgrade core-js from 3.6.5 to 3.35.1 #159
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 was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade core-js from 3.6.5 to 3.35.1.
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
✨ Snyk has automatically assigned this pull request, set who gets assigned.
ℹ️ 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.35.1 - 2024-01-20
- Fixed internal
- Removed significant redundant code from
- Fixed setting names of methods with symbol keys in some old engines
- Minor fix of prototype methods export logic in the pure version
- Compat data improvements:
- Note that V8 ~ Chrome 122 add
- Added Oculus Quest Browser 31 compat data mapping
- Updated Electron 29 and added Electron 30 compat data mapping
-
3.35.0 - 2023-12-28
- Fixed handling some cases of non-enumerable symbol keys from
- Removed unneeded NodeJS domains-related logic from
- Fixed subclassing of wrapped
- Refactoring, many different minor optimizations
- Compat data improvements:
- It seems that the ancient
- Since
- Added Opera Android 80 and updated Opera Android 79 compat data mapping
- Added Samsung Internet 24 compat data mapping
-
3.34.0 - 2023-12-05
- Methods:
- Moved to stable ES, November 2023 TC39 meeting
- Added
- Method:
- Moved to stable ES, November 2023 TC39 meeting
- Added
- Fixed a web incompatibility issue of
- Added
- Methods:
- Relaxed some specific cases of
- Fixed
- Fixed the order of arguments validation in
- Some minor
- Compat data improvements:
-
3.33.3 - 2023-11-19
- Fixed an issue getting the global object on Duktape, #1303
- Avoid sharing internal
- Some internal untangling
- Compat data improvements:
- Added Deno 1.38 compat data mapping
- Added Opera Android 79 compat data mapping
- Added Oculus Quest Browser 30 compat data mapping
- Updated Electron 28 and 29 compat data mapping
-
3.33.2 - 2023-10-30
- Simplified
- Added support of
- Removed unspecified unnecessary
- Fixed handling of fractional number part in
- Compat data improvements:
- Updated Opera Android 78 compat data mapping
- Added Electron 29 compat data mapping
-
3.33.1 - 2023-10-20
- Added one more workaround of possible error with
- Directly specified
- Prevented potential issue with lack of some dependencies after automatic optimization polyfills of some methods in the pure version
- Some minor internal fixes and optimizations
- Compat data improvements:
- Added React Native 0.73 Hermes compat data, mainly fixes of some issues
- Added NodeJS 21.0 compat data mapping
-
3.33.0 - 2023-10-01
- Re-introduced
- Added
- Some years ago, it was presented in
- Added
- Optimized
- Fixed some conversion cases of
- Fully forced polyfilling of the TC39
- Added an extra workaround of errors with exotic environment objects in
- Some minor fixes and stylistic changes
- Compat data improvements:
- V8 unshipped
- Added Deno 1.37 compat data mapping
- Added Electron 28 compat data mapping
- Added Opera Android 78 compat data mapping
-
3.32.2 - 2023-09-07
- Fixed
- Added a workaround of old WebKit +
- Compat data improvements:
- Added Samsung Internet 23 compat data mapping
- Added Quest Browser 29 compat data mapping
-
3.32.1 - 2023-08-18
- Fixed some cases of IEEE754 rounding, #1279, thanks @ petamoriken
- Prevented injection
- Some minor fixes and stylistic changes
- Compat data improvements:
- Added Opera Android 77 compat data mapping
- Updated Electron 27 compat data mapping
-
3.32.0 - 2023-07-27
- Moved back to stage 3
- Added
- Moved to stage 3
- Added
- Throw on negative
- Removed
- Iterator Helpers stage 3 proposal:
- Avoid creating observable
- Async explicit resource management:
- Moved back into the initial proposal -> moved to stage 3, proposal-explicit-resource-management/154
- Added
- Ignore return value of
- Added ticks for empty resources, proposal-explicit-resource-management/163
- Added some methods from
- There are some reason why I don't want to add
- Methods:
- Added
- Methods:
- Used strict mode in some missed cases, #1269
- Fixed a Chromium 117 bug in
- Fixed early WebKit ~ Safari 17.0 beta
- Fixed incorrect
- Fixed forced polyfilling of some iterator helpers that should return wrapped iterator in the pure version
- Fixed and exposed
- Compat data improvements:
- Sync
- Mark
- Added Electron 27 compat data mapping
-
3.31.1 - 2023-07-06
-
3.31.0 - 2023-06-11
-
3.30.2 - 2023-05-06
-
3.30.1 - 2023-04-13
-
3.30.0 - 2023-04-03
-
3.29.1 - 2023-03-13
-
3.29.0 - 2023-02-26
-
3.28.0 - 2023-02-13
-
3.27.2 - 2023-01-18
-
3.27.1 - 2022-12-29
-
3.27.0 - 2022-12-25
-
3.26.1 - 2022-11-13
-
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
-
3.20.3 - 2022-01-15
-
3.20.2 - 2022-01-01
-
3.20.1 - 2021-12-23
-
3.20.0 - 2021-12-15
-
3.19.3 - 2021-12-06
-
3.19.2 - 2021-11-29
-
3.19.1 - 2021-11-02
-
3.19.0 - 2021-10-25
-
3.18.3 - 2021-10-12
-
3.18.2 - 2021-10-05
-
3.18.1 - 2021-09-26
-
3.18.0 - 2021-09-19
-
3.17.3 - 2021-09-09
-
3.17.2 - 2021-09-02
-
3.17.1 - 2021-09-01
-
3.17.0 - 2021-09-01
-
3.16.4 - 2021-08-29
-
3.16.3 - 2021-08-24
-
3.16.2 - 2021-08-17
-
3.16.1 - 2021-08-08
-
3.16.0 - 2021-07-30
-
3.15.2 - 2021-06-29
-
3.15.1 - 2021-06-22
-
3.15.0 - 2021-06-20
-
3.14.0 - 2021-06-05
-
3.13.1 - 2021-05-29
-
3.13.0 - 2021-05-25
-
3.12.1 - 2021-05-08
-
3.12.0 - 2021-05-06
-
3.11.3 - 2021-05-05
-
3.11.2 - 2021-05-03
-
3.11.1 - 2021-04-28
-
3.11.0 - 2021-04-22
-
3.10.2 - 2021-04-19
-
3.10.1 - 2021-04-07
-
3.10.0 - 2021-03-31
-
3.9.1 - 2021-02-28
-
3.9.0 - 2021-02-18
-
3.8.3 - 2021-01-19
-
3.8.2 - 2021-01-03
-
3.8.1 - 2020-12-06
-
3.8.0 - 2020-11-25
-
3.7.0 - 2020-11-06
-
3.6.5 - 2020-04-09
from core-js GitHub release notesToLengthoperation with bigints, #1318String#splitpolyfillIteratorhelpers proposal methods marked as supported from V8 ~ Chrome 122Setmethods, but they have a bug similar to Safariselfmarked as fixed from Bun 1.0.22SuppressedErrorandSymbol.{ dispose, asyncDispose }marked as supported from Bun 1.0.23{ Map, Set, WeakMap, WeakSet }.{ from, of }became non-generic, following this and some other notes. Now they can be invoked withoutthis, but no longer return subclass instancesSymbolpolyfillqueueMicrotaskpolyfillArrayBufferArray.fromAsyncmarked as supported from V8 ~ Chrome 121Array.prototype.pushbug is fixed in V8 ~ Chrome 122 (Hallelujah!)ArrayBuffer.prototype.transferand friends proposal features marked as supported from FF 122 and Bun 1.0.19Object.groupByandMap.groupBymarked as supported from Bun 1.0.19Iteratorhelpers proposal methods are still not disabled in Deno, the web compatibility issue why it was disabled in Chromium makes no sense for Deno and fixed in the spec, they marked as supported from Deno 1.37Arraygrouping proposal:Object.groupByMap.groupByes.namespace modules,/es/and/stable/namespaces entriesPromise.withResolversproposal:Promise.withResolverses.namespace module,/es/and/stable/namespaces entriesIteratorhelpers proposal, proposal-iterator-helpers/287 and some following changes, November 2023 TC39 meetingUint8Arrayto / from base64 and hex stage 2 proposal:Uint8Array.fromBase64Uint8Array.fromHexUint8Array.prototype.toBase64Uint8Array.prototype.toHexNumber.fromStringvalidation before clarification of proposal-number-fromstring/24@@ toStringTagproperty descriptors on DOM collections, #1312Arrayiteration methods, #1313atob/btoaimprovementsPromise.withResolversmarked as shipped from FF121[[DedentMap]]fromString.dedentproposal betweencore-jsinstances before stabilization of the proposalArray.fromAsyncmarked as supported from Deno 1.38Symbol.{ dispose, asyncDispose }marked as supported from Deno 1.38structuredClonepolyfill, avoided second tree pass in cases of transferringSuppressedErrortostructuredClonepolyfillArrayBufferandDataViewdependencies ofstructuredClonelack of which could cause errors in some entries in IE10-Number.fromStringURL.canParsemarked as supported from Chromium 120Symbolpolyfill on global object, #1289type: commonjsinpackage.jsonof all packages to avoid potential breakage in future Node versions, see this issueString.prototype.{ isWellFormed, toWellFormed }marked as supported from FF119RegExpescaping stage 2 proposal, September 2023 TC39 meeting:RegExp.escapemethod with the new set of symbols for escapingcore-js, but it was removed after rejecting the old version of this proposalArrayBuffer.prototype.{ transfer, transferToFixedLength }and support transferring ofArrayBuffers viastructuredCloneto engines withMessageChannelMath.f16roundpolyfillMath.f16roundandDataView.prototype.{ getFloat16, setFloat16 }Observableproposal because of incompatibility with the new WHATWGObservableproposalSymbolpolyfill, #1289Iteratorhelpers because of some Web compatibility issuesPromise.withResolversmarked as supported from V8 ~ Chrome 119Arraygrouping proposal features marked as supported from FF119valueargument ofURLSearchParams.prototype.{ has, delete }marked as properly supported from V8 ~ Chrome 118URL.canParseandURLSearchParams.prototype.sizemarked as supported from Bun 1.0.2structuredClonefeature detection[email protected]bug, #1288evalbug, #1287processpolyfill tocore-jsvia some bundlers oresm.sh, #1277Promise.withResolversmarked as supported from Bun 0.7.1Arraygrouping proposal, July 2023 TC39 meeting updates:/actual/namespaces entries, unconditional forced replacement changed to feature detectionPromise.withResolversproposal, July 2023 TC39 meeting updates:/actual/namespaces entries, unconditional forced replacement changed to feature detectionSetmethods stage 3 proposal, July 2023 TC39 meeting updates::Setsizes, proposal-set-methods/88IsCallablecheck inGetKeysIterator, proposal-set-methods/101Stringwrapper objects, July 2023 TC39 meeting update, proposal-iterator-helpers/281Iteratoris not constructible from the active function object (works as an abstract class)/actual/namespace entries, unconditional forced replacement changed to feature detection[@@ dispose]()method when hint isasync-dispose, proposal-explicit-resource-management/180Float16Arraystage 3 proposal:Float16Arrayright now, however, make sense to add some methods from this proposal.Math.f16roundDataView.prototype.getFloat16DataView.prototype.setFloat16DataViewget / setUint8Clampedmethods stage 1 proposal:DataView.prototype.getUint8ClampedDataView.prototype.setUint8Clampedvalueargument ofURLSearchParams.prototype.{ has, delete }Setmethods implementation by the actual specSymbol.{ dispose, asyncDispose }descriptors from NodeJS 20.4 / transpilers helpers / userland codeAsyncIteratorPrototypecore-js/configuratoroption, #1268Iteratorhelpers proposal features marked as supported from V8 ~ Chrome 117Arraygrouping proposal features marked as supported from V8 ~ Chrome 117Symbol.{ dispose, asyncDispose }as supported from NodeJS 20.5.0 (as mentioned above, NodeJS 20.4.0 add it, but with incorrect descriptors)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
👩💻 Set who automatically gets assigned
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs