Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade core-js from 3.21.1 to 3.22.0 #343

Merged
merged 1 commit into from Apr 25, 2022

Conversation

rafa8626
Copy link
Member

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.0.

merge advice
ℹ️ 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.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 2 days ago, on 2022-04-15.
Release notes
Package name: core-js
  • 3.22.0 - 2022-04-15
    • Change Array by copy proposal:
      • Moved to Stage 3, March TC39 meeting
      • Disabled forced replacement and added /actual/ entry points for methods from this proposal
      • Array.prototype.toSpliced throws a TypeError instead of RangeError if the result length is more than MAX_SAFE_INTEGER, proposal-change-array-by-copy/70
    • Added some more atob / btoa fixes:
      • NodeJS <17.9 atob does not ignore spaces, node/42530
      • Actual NodeJS atob does not validate encoding, node/42646
      • FF26- implementation does not properly convert argument to string
      • IE / Edge <16 implementation have wrong arity
    • Added /full/ namespace as the replacement for /features/ since it's more descriptive in context of the rest namespaces (/es//stable//actual//full/)
    • Avoided propagation of removed parts of proposals to upper stages. For example, %TypedArray%.prototype.groupBy was removed from the Array grouping 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.
    • 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 Error features with wrapped Error constructors, #1061
      • null and undefined allowed as the second argument of structuredClone, #1056
    • Tooling:
      • Stabilized proposals are filtered out from the core-js-compat -> core-js-builder -> core-js-bundle output. 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.
      • Aligned modules filters of core-js-builder and core-js-compat, now it's modules and exclude options
      • Added support of entry points, modules, regexes, and arrays of them to those filters
      • Missed targets option of core-js-compat means that the targets filter just will not be applied, so the result will contain modules required for all possible engines
    • Compat data:
      • .stack property on DOMException marked as supported from Deno 1.15
      • 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 Array.prototype.{ groupBy, groupByToMap } implementation
    • core-js-compat targets parser transforms engine names to lower case
    • atob / btoa marked as fixed in NodeJS 17.5
    • Added Electron 18.0 compat data mapping
    • Added Deno 1.20 compat data mapping
from core-js GitHub release notes
Commit messages
Package name: core-js
  • c5e56b6 3.22.0
  • 01b057c update entries in the readme
  • 06c6a56 use `import` in some examples
  • 0f3c603 avoid propagation of removed parts of proposals to upper stages
  • 24d2e5d drop splitted / renamed modules from `modules-by-versions`
  • 8c91bab update dependencies
  • 1e07b0c add`get-modules-list-for-target-version` tests
  • eff765f disable forced replacement for methods from "Change `Array` by copy" proposal
  • a7aab7f use `import` instead of `require`
  • 7717637 add some tests
  • 551a129 align modules filters of `core-js-builder` and `core-js-compat`
  • 3cad08a some improvements of `core-js-compat/compat` tool
  • e605083 update dependencies
  • 6293e75 update dependencies
  • e5aeee7 temporally revert `/features/` -> `/full/` from the readme for avoid confusing
  • 1d63660 add `/features/` to `.gitignore`
  • 1f2c023 add `/full/` namespace as the replacement for `/features/`
  • 1f6985c one more `atob` bug on NodeJS
  • d1687e7 add a comment
  • 6edcde9 some more `atob` / `btoa` fixes
  • edc328b update dependencies
  • 25e7811 add Samsung Internet 17.0 compat data mapping
  • 1506450 add Deno runner for compat tests
  • d14fdb8 change the structure of the changelog

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

@rafa8626 rafa8626 merged commit 58f3724 into master Apr 25, 2022
@rafa8626 rafa8626 deleted the snyk-upgrade-2c4860ba208e783b894514b78e0c1a0f branch April 25, 2022 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants