[Snyk] Upgrade core-js from 3.6.5 to 3.27.2 #3
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.6.5 to 3.27.2. See this package in npm: https://www.npmjs.com/package/core-js See this project in Snyk: https://app.snyk.io/org/qmutz/project/cf4c7dbe-da03-486a-b4c5-4b22171d233b?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
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.27.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.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
- Iterator Helpers proposal:
- Built-ins:
- Moved to Stage 3, November 2022 TC39 meeting
- Added
- Built-ins:
- Moved to Stage 3, November 2022 TC39 meeting
- Reimplemented with new semantics:
- Optimized performance (iteration over lowest set)
- Accepted only
- Accepted only
- Added
- For avoiding breaking changes:
- New versions of methods are implemented as new modules and available in new entries or entries where old versions of methods were not available before (like
- In entries where they were available before (like
- Well-Formed Unicode Strings proposal:
- Methods:
- Moved to Stage 3, November 2022 TC39 meeting
- Added
- Explicit resource management Stage 3 and Async explicit resource management Stage 2 proposals:
- Renamed from "
- In addition to already present well-known symbols, added new built-ins:
- Sync version of this proposal moved to Stage 3, November 2022 TC39 meeting
- Added
- Added
- Method
- Throws an error on non-frozen raw templates for avoiding possible breaking changes in the future, proposal-string-dedent/75
- Compat data targets improvements:
- React Native from 0.70 shipped with Hermes as the default engine. However, bundled Hermes versions differ from standalone Hermes releases. So added
- According to the documentation, Oculus Browser was renamed to Meta Quest Browser, so
- For consistency with two previous cases, added
- For avoiding breaking changes, the
- Compat data improvements:
- Change
- Added Deno 1.28 / 1.29 compat data mapping
- Added NodeJS 19.2 compat data mapping
- Added Samsung Internet 19.0 compat data mapping
- Added Quest Browser 24.0 compat data mapping
- Fixed the first version in the Chromium-based Edge compat data mapping
- Smoothed behavior of some conflicting proposals
- Removed some generic behavior (like
- Added pure version of the
- Added
- Fixed handling of sparse arrays in
- Fixed a theoretically possible future conflict of polyfills definitions in the pure version
- Some refactoring and optimization
-
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
- Moved to Stage 3, September TC39 meeting
- Avoid observable side effects of
- Added well-formed unicode strings stage 2 proposal:
- Recent updates of the iterator helpers proposal:
- Added a counter parameter to helpers, proposal-iterator-helpers/211
- Don't await non-objects returned from functions passed to
- Early exit on broken
- Added
- Added
- Added
- Added NodeJS 19.0 compat data
- Added Deno 1.26 and 1.27 compat data
- Added Opera Android 72 compat data mapping
- Updated Electron 22 compat data mapping
-
3.25.5 - 2022-10-03
- Fixed regression with an error on reuse of some built-in methods from another realm, #1133
-
3.25.4 - 2022-10-02
- Added a workaround of a Nashorn bug with
- Updated lists of
- Added Electron 22 compat data mapping
-
3.25.3 - 2022-09-25
- Forced polyfilling of
- Fixed existence of
- Added Opera Android 71 compat data mapping
- Some stylistic changes
-
3.25.2 - 2022-09-18
- Considering
- Added Safari 16.0 compat data
- Added iOS Safari 16.0 compat data mapping
- Fixed some ancient iOS Safari versions compat data mapping
-
3.25.1 - 2022-09-07
- Added some fixes and workarounds of FF30- typed arrays bug that does not properly convert objects to numbers
- Added
- Dropped
- Added Bun 0.1.6-0.1.11 compat data
- Added Deno 1.25 compat data mapping
- Updated Electron 21 compat data mapping
- Some stylistic changes, minor fixes, and improvements
-
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 notesSetmethods 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 EdgeIteratorIterator.fromIterator.prototype.dropIterator.prototype.everyIterator.prototype.filterIterator.prototype.findIterator.prototype.flatMapIterator.prototype.forEachIterator.prototype.mapIterator.prototype.reduceIterator.prototype.someIterator.prototype.takeIterator.prototype.toArrayIterator.prototype.toAsyncIterator.prototype[@@ toStringTag]AsyncIteratorAsyncIterator.fromAsyncIterator.prototype.dropAsyncIterator.prototype.everyAsyncIterator.prototype.filterAsyncIterator.prototype.findAsyncIterator.prototype.flatMapAsyncIterator.prototype.forEachAsyncIterator.prototype.mapAsyncIterator.prototype.reduceAsyncIterator.prototype.someAsyncIterator.prototype.takeAsyncIterator.prototype.toArrayAsyncIterator.prototype[@@ toStringTag]/actual/entries, unconditional forced replacement disabled for features that survived to Stage 3.fromaccept strings,.flatMapthrows on strings returned from the callback, proposal-iterator-helpers/244, proposal-iterator-helpers/250.fromand.flatMapthrows on non-object iterators, proposal-iterator-helpers/253Setmethods proposal:Set.prototype.intersectionSet.prototype.unionSet.prototype.differenceSet.prototype.symmetricDifferenceSet.prototype.isSubsetOfSet.prototype.isSupersetOfSet.prototype.isDisjointFromSet-like objects as an argument, not all iterablesSets asthis, no@@ speciessupport, and other minor changes/actual/entries, unconditional forced replacement changed to feature detection/actual/namespace)/full/namespace), those methods are available with fallbacks to old semantics (in addition toSet-like, they accept iterable objects). This behavior will be removed from the next major releaseString.prototype.isWellFormedString.prototype.toWellFormed/actual/entries, disabled unconditional forced replacementusingstatement" and splitted into 2 (sync and async) proposalsSymbol.disposeSymbol.asyncDisposeSuppressedErrorDisposableStackDisposableStack.prototype.disposeDisposableStack.prototype.useDisposableStack.prototype.adoptDisposableStack.prototype.deferDisposableStack.prototype.moveDisposableStack.prototype[@@ dispose]AsyncDisposableStackAsyncDisposableStack.prototype.disposeAsyncAsyncDisposableStack.prototype.useAsyncDisposableStack.prototype.adoptAsyncDisposableStack.prototype.deferAsyncDisposableStack.prototype.moveAsyncDisposableStack.prototype[@@ asyncDispose]Iterator.prototype[@@ dispose]AsyncIterator.prototype[@@ asyncDispose]/actual/namespace entries for Stage 3 proposalString.dedentstage 2 proposalString.dedentreact-nativetarget for React Native with bundled Hermes.oculustarget was renamed toquest.opera_mobiletarget name is confusing since it contains data for the Chromium-based Android version, but iOS Opera is Safari-based. Soopera_mobiletarget was renamed toopera-android.androidtarget name is also confusing for someone - that means Android WebView, some think thinks that it's Chrome for Android, but they have some differences. For avoiding confusion, addedchrome-androidtarget.firefox-androidtarget.oculusandopera_mobilefields are available in the compat data till the next major release.Array.fromAsyncmarked as supported from Bun 0.3.0String.prototype.{ isWellFormed, toWellFormed }marked as supported from Bun 0.4.0Arrayby copy proposal marked as supported from Deno 1.27, deno/16429{ Map, WeakMap }.prototype.emplacebecame stricter by the spec draft@@ speciespattern) of some.prototypemethods from the new collections methods proposal and theArraydeduplication proposal that most likely will not be implemented since it contradicts the current TC39 policyNumberconstructor, #1154, #1155, thanks @ trososset(Timeout|Interval|Immediate)extra arguments fix for Bun 0.3.0- (similarly to IE9-), bun/1633structuredClone, #1156Array.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/44Array.fromAsyncproposal:%Array.prototype.values%usage in array-like branch, proposal-array-from-async/30String.prototype.isWellFormedString.prototype.toWellFormedAsyncIteratorhelpers, proposal-iterator-helpers/239{ Iterator, AsyncIterator }.prototype.flatMapsupports returning both - iterables and iterators, proposal-iterator-helpers/233.nextin missed cases of{ Iterator, AsyncIterator }.from, proposal-iterator-helpers/232selfpolyfill as a part of The Minimum Common Web Platform API, specification, #1118inverseoption tocore-js-compat, #1119formatoption tocore-js-builder, #1120Function.prototype.{ call, apply, bind }on string methods, #1128[Serializable]and[Transferable]objects in thestructuredClonepolyfill. Mainly, for better error messages if polyfilling of cloning such types is impossibleArray.prototype.{ group, groupToMap }marked as supported from V8 ~ Chromium 108Array.prototype.groupToMapin the pure version for returning wrappedMapinstancesArray.prototype.{ findLast, findLastIndex }in/stage/4entrydocument.allas a callable in some missed casessideEffectsfield tocore-js-purepackage.jsonfor better tree shaking, #1117semverdependency fromcore-js-compatsemverpackage (ironically) added a breaking change and dropped NodeJS 8 support in the minor7.1version, after thatsemverincore-js-compatwas pinned to7.0since for avoiding breaking changes it should support NodeJS 8. However, sincecore-js-compatis usually used with other packages that usesemverdependency, it causes multiple duplications ofsemverin dependencies. So I decided to removesemverdependency and replace it with a couple of simple helpers.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