[Snyk] Upgrade core-js from 3.21.1 to 3.22.2 #118
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.21.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
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.5Commit 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