[Snyk] Upgrade core-js from 3.2.1 to 3.22.2 #67
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.2.1 to 3.22.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.22.2 - 2022-04-21
- Fixed
- Fixed
-
3.22.1 - 2022-04-19
- Improved some cases of
- Prevented experimental warning in NodeJS ~ 18.0 on detection
- Added NodeJS 18.0 compat data
-
3.22.0 - 2022-04-15
- Change
- Moved to Stage 3, March TC39 meeting
- Disabled forced replacement and added
- Added some more
- NodeJS <17.9
- Actual NodeJS
- FF26- implementation does not properly convert argument to string
- IE / Edge <16 implementation have wrong arity
- Added
- Avoided propagation of removed parts of proposals to upper stages. For example,
- Significant internal refactoring and splitting of modules (but without exposing to public API since it will be a breaking change - it will be exposed in the next major version)
- Bug fixes:
- Fixed work of non-standard V8
- Tooling:
- Stabilized proposals are filtered out from the
- Aligned modules filters of
- Added support of entry points, modules, regexes, and arrays of them to those filters
- Missed
- Compat data:
- Added Deno 1.21 compat data mapping
- Added Electron 19.0 and updated 18.0 compat data mapping
- Added Samsung Internet 17.0 compat data mapping
- Added Opera Android 68 compat data mapping
-
3.21.1 - 2022-02-16
- Added a bugfix for the WebKit
- Added Electron 18.0 compat data mapping
- Added Deno 1.20 compat data mapping
-
3.21.0 - 2022-02-01
- Added Base64 utility methods:
- Added the proper validation of arguments to some methods from web standards
- Forced replacement of all features from early-stage proposals for avoiding possible web compatibility issues in the future
- Added Rhino 1.7.14 compat data
- Added Deno 1.19 compat data mapping
- Added Opera Android 66 and 67 compat data mapping
- Added iOS Safari 15.3 and 15.4 compat data mapping
-
3.20.3 - 2022-01-15
- Detects and replaces broken third-party
- Changed the structure of notes in
-
3.20.2 - 2022-01-01
- Added a fix of a V8 ~ Chrome 36-
- Added fixes of some different
-
3.20.1 - 2021-12-23
- Fixed the order of calling reactions of already fulfilled / rejected promises in
- Fixed possible memory leak in specific promise chains
- Fixed some missed dependencies of entries
- Added Deno 1.18 compat data mapping
-
3.20.0 - 2021-12-15
- Added
- Includes all cases of cloning and transferring of required ECMAScript and platform types that can be polyfilled, for the details see the caveats
- Uses native structured cloning algorithm implementations where it's possible
- Includes the new semantic of errors cloning from
- Added
- Includes
- Includes
- Reuses native
- Added support of
- Added
- Added
- Moved to stage 3
- Added
- Removed
- Added change
- Added
- Added
- Added
- Added
- Added a workaround of most cases breakage modern
- Fixed
- Fixed validation of typed arrays in typed arrays iteration methods in V8 ~ Chrome 50-
- Extension of the API, #1012
- Added a new
- Added entry points for each finished post-ES6 proposal
-
3.19.3 - 2021-12-06
- Fixed internal slots check in methods of some built-in types, #1017
- Fixed
- Refactored
- Added NodeJS 17.2 compat data mapping
-
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
-
3.6.4 - 2020-01-13
-
3.6.3 - 2020-01-10
-
3.6.2 - 2020-01-06
-
3.6.1 - 2019-12-25
-
3.6.0 - 2019-12-18
-
3.5.0 - 2019-12-12
-
3.4.8 - 2019-12-08
-
3.4.7 - 2019-12-02
-
3.4.6 - 2019-12-02
-
3.4.5 - 2019-11-27
-
3.4.4 - 2019-11-27
-
3.4.3 - 2019-11-26
-
3.4.2 - 2019-11-21
-
3.4.1 - 2019-11-12
-
3.4.0 - 2019-11-06
-
3.3.6 - 2019-10-31
-
3.3.5 - 2019-10-28
-
3.3.4 - 2019-10-25
-
3.3.3 - 2019-10-21
-
3.3.2 - 2019-10-14
-
3.3.1 - 2019-10-13
-
3.3.0 - 2019-10-13
-
3.2.1 - 2019-08-12
from core-js GitHub release notesURLSearchParamsin IE8- that was broken in the previous release__lookupGetter__entriesRegExpflags handlingfetchAPIArrayby copy proposal:/actual/entry points for methods from this proposalArray.prototype.toSplicedthrows aTypeErrorinstead ofRangeErrorif the result length is more thanMAX_SAFE_INTEGER, proposal-change-array-by-copy/70atob/btoafixes:atobdoes not ignore spaces, node/42530atobdoes not validate encoding, node/42646/full/namespace as the replacement for/features/since it's more descriptive in context of the rest namespaces (/es/⊆/stable/⊆/actual/⊆/full/)%TypedArray%.prototype.groupBywas removed from theArraygrouping proposal a long time ago. We can't completely remove this method since it's a breaking change. But this proposal has been promoted to stage 3 - so the proposal should be promoted without this method, this method should not be available in/actual/entries - but it should be available in early-stage entries to avoid breakage.Errorfeatures with wrappedErrorconstructors, #1061nullandundefinedallowed as the second argument ofstructuredClone, #1056core-js-compat->core-js-builder->core-js-bundleoutput. That mean that if the output contains, for example,es.object.has-own, the legacy reference to it,esnext.object.has-own, no longer added.core-js-builderandcore-js-compat, now it'smodulesandexcludeoptionstargetsoption ofcore-js-compatmeans that thetargetsfilter just will not be applied, so the result will contain modules required for all possible engines.stackproperty onDOMExceptionmarked as supported from Deno 1.15Array.prototype.{ groupBy, groupByToMap }implementationcore-js-compattargets parser transforms engine names to lower caseatob/btoamarked as fixed in NodeJS 17.5atobbtoaFunction#bindpolyfills, uses only nativeFunction#bindin the internalsstructuredCloneshould throw an error if no arguments passed__core-js_shared__Object.{ defineProperty, defineProperties }bug, Babel issue%TypedArray%.prototype.setbugs, affects modern engines (like Chrome < 95 or Safari < 14.1)Promise.prototype.then, #1026structuredClonemethod from the HTML spec, see MDNhtml/5749DOMExceptionpolyfill, the Web IDL spec, see MDNDOMExceptionand its attributes polyfills with fixes of many different engines bugsDOMException#stackproperty polyfill in engines that should have itDOMExceptionimplementations where it's possible (for example, in old NodeJS where it's not exposed as global)causeon all Error typesError.prototype.toStringmethod polyfill with fixes of many different bugs of JS enginesNumber.prototype.toExponentialmethod polyfill with fixes of many different bugs of JS enginesArraygrouping proposal:Array.prototype.groupByToMapmethod@@ speciessupportArrayby copy stage 2 proposal:Array.prototype.toReversedArray.prototype.toSortedArray.prototype.toSplicedArray.prototype.with%TypedArray%.prototype.toReversed%TypedArray%.prototype.toSorted%TypedArray%.prototype.toSpliced%TypedArray%.prototype.withIterator.prototype.toAsyncmethod from the iterator helpers stage 2 proposalArray.fromAsyncproposal moved to stage 2String.cookedstage 1 proposal:Function.prototype.unThisstage 0 proposalFunction.{ isCallable, isConstructor }stage 0 proposal:Function.isCallableFunction.isConstructorString#atafter loading obsoleteString#atproposal module, #1019Array.prototype.{ values, @@ iterator }.namein V8 ~ Chrome 45-core-js/actual/**namespaceURLSearchParamsiterator.nextthat should be enumerable by the specSubscriptionNote: 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