arthur/website-old
1
0
Fork 0
mirror of https://github.com/ArthurDanjou/website-old.git synced 2026-01-14 12:14:42 +01:00
Code Issues 31 Packages Projects Releases Wiki Activity

[PR #244] fix(deps): bump core-js from 3.20.2 to 3.22.1 #255

New Issue
Closed
opened 2025-12-01 17:06:31 +01:00 by arthur · 0 comments
arthur commented 2025-12-01 17:06:31 +01:00
Owner
Copy Link

Original Pull Request: https://github.com/ArthurDanjou/website-old/pull/244

State: closed
Merged: No

Bumps core-js from 3.20.2 to 3.22.1.

Changelog

Sourced from core-js's changelog.

3.22.1 - 2022.04.20
  • Improved some cases of RegExp flags handling
  • Prevented experimental warning in NodeJS ~ 18.0 on detection fetch API
  • Added NodeJS 18.0 compat data
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.17
  • 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
3.21.0 - 2022.02.02
  • Added Base64 utility methods:
    • atob
    • btoa
  • 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

... (truncated)

Commits
  • 48aafd0 3.22.1
  • 3e61cd2 prevent experimental warning in NodeJS ~ 18.0 on detection fetch API
  • 691125e add NodeJS 18.0 compat data
  • e4aa626 make tests work on NodeJS 18
  • 6844ba3 update dependencies
  • a0f8ce1 add NodeJS 18.0 compat data mapping
  • 862f06a prevent crash with unexist browser
  • 2c3dcf0 update dependencies
  • 889643e improve some cases of RegExp flags handling
  • a9dc769 take into account .hasIndices regex flag
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
**Original Pull Request:** https://github.com/ArthurDanjou/website-old/pull/244 **State:** closed **Merged:** No --- Bumps [core-js](https://github.com/zloirock/core-js) from 3.20.2 to 3.22.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zloirock/core-js/blob/master/CHANGELOG.md">core-js's changelog</a>.</em></p> <blockquote> <h5>3.22.1 - 2022.04.20</h5> <ul> <li>Improved some cases of <code>RegExp</code> flags handling</li> <li>Prevented experimental warning in NodeJS ~ 18.0 on detection <code>fetch</code> API</li> <li>Added NodeJS 18.0 compat data</li> </ul> <h5>3.22.0 - 2022.04.15</h5> <ul> <li><a href="https://github.com/tc39/proposal-change-array-by-copy">Change <code>Array</code> by copy proposal</a>: <ul> <li>Moved to Stage 3, <a href="https://github-redirect.dependabot.com/babel/proposals/issues/81#issuecomment-1083449843">March TC39 meeting</a></li> <li>Disabled forced replacement and added <code>/actual/</code> entry points for methods from this proposal</li> <li><code>Array.prototype.toSpliced</code> throws a <code>TypeError</code> instead of <code>RangeError</code> if the result length is more than <code>MAX_SAFE_INTEGER</code>, <a href="https://github-redirect.dependabot.com/tc39/proposal-change-array-by-copy/pull/70">proposal-change-array-by-copy/70</a></li> </ul> </li> <li>Added some more <code>atob</code> / <code>btoa</code> fixes: <ul> <li>NodeJS &lt;17.9 <code>atob</code> does not ignore spaces, <a href="https://github-redirect.dependabot.com/nodejs/node/issues/42530">node/42530</a></li> <li>Actual NodeJS <code>atob</code> does not validate encoding, <a href="https://github-redirect.dependabot.com/nodejs/node/issues/42646">node/42646</a></li> <li>FF26- implementation does not properly convert argument to string</li> <li>IE / Edge &lt;16 implementation have wrong arity</li> </ul> </li> <li>Added <code>/full/</code> namespace as the replacement for <code>/features/</code> since it's more descriptive in context of the rest namespaces (<code>/es/</code> ⊆ <code>/stable/</code> ⊆ <code>/actual/</code> ⊆ <code>/full/</code>)</li> <li>Avoided propagation of removed parts of proposals to upper stages. For example, <code>%TypedArray%.prototype.groupBy</code> was removed from the <code>Array</code> 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 <code>/actual/</code> entries - but it should be available in early-stage entries to avoid breakage.</li> <li>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)</li> <li>Bug fixes: <ul> <li>Fixed work of non-standard V8 <code>Error</code> features with wrapped <code>Error</code> constructors, <a href="https://github-redirect.dependabot.com/zloirock/core-js/issues/1061">#1061</a></li> <li><code>null</code> and <code>undefined</code> allowed as the second argument of <code>structuredClone</code>, <a href="https://github-redirect.dependabot.com/zloirock/core-js/issues/1056">#1056</a></li> </ul> </li> <li>Tooling: <ul> <li>Stabilized proposals are filtered out from the <code>core-js-compat</code> -&gt; <code>core-js-builder</code> -&gt; <code>core-js-bundle</code> output. That mean that if the output contains, for example, <code>es.object.has-own</code>, the legacy reference to it, <code>esnext.object.has-own</code>, no longer added.</li> <li>Aligned modules filters of <a href="https://github.com/zloirock/core-js/tree/master/packages/core-js-builder"><code>core-js-builder</code></a> and <a href="https://github.com/zloirock/core-js/tree/master/packages/core-js-compat"><code>core-js-compat</code></a>, now it's <code>modules</code> and <code>exclude</code> options</li> <li>Added support of entry points, modules, regexes, and arrays of them to those filters</li> <li>Missed <code>targets</code> option of <code>core-js-compat</code> means that the <code>targets</code> filter just will not be applied, so the result will contain modules required for all possible engines</li> </ul> </li> <li>Compat data: <ul> <li><code>.stack</code> property on <code>DOMException</code> marked as supported from Deno <a href="https://github.com/denoland/deno/releases/tag/v1.15.0">1.15</a></li> <li>Added Deno 1.21 compat data mapping</li> <li>Added Electron 19.0 and updated 18.0 compat data mapping</li> <li>Added Samsung Internet 17.0 compat data mapping</li> <li>Added Opera Android 68 compat data mapping</li> </ul> </li> </ul> <h5>3.21.1 - 2022.02.17</h5> <ul> <li>Added a <a href="https://bugs.webkit.org/show_bug.cgi?id=236541">bug</a>fix for the WebKit <code>Array.prototype.{ groupBy, groupByToMap }</code> implementation</li> <li><code>core-js-compat</code> targets parser transforms engine names to lower case</li> <li><code>atob</code> / <code>btoa</code> marked as <a href="https://github-redirect.dependabot.com/nodejs/node/pull/41478">fixed</a> in NodeJS 17.5</li> <li>Added Electron 18.0 compat data mapping</li> <li>Added Deno 1.20 compat data mapping</li> </ul> <h5>3.21.0 - 2022.02.02</h5> <ul> <li>Added <a href="https://developer.mozilla.org/en-US/docs/Glossary/Base64">Base64 utility methods</a>: <ul> <li><code>atob</code></li> <li><code>btoa</code></li> </ul> </li> <li>Added the proper validation of arguments to some methods from web standards</li> <li>Forced replacement of all features from early-stage proposals for avoiding possible web compatibility issues in the future</li> <li>Added Rhino 1.7.14 compat data</li> <li>Added Deno 1.19 compat data mapping</li> <li>Added Opera Android 66 and 67 compat data mapping</li> <li>Added iOS Safari 15.3 and 15.4 compat data mapping</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zloirock/core-js/commit/48aafd056bb4fbe0ea749d0ad371b15dd2cf51fc"><code>48aafd0</code></a> 3.22.1</li> <li><a href="https://github.com/zloirock/core-js/commit/3e61cd2642bfe1b5446a3d320e4f912614cd098f"><code>3e61cd2</code></a> prevent experimental warning in NodeJS ~ 18.0 on detection <code>fetch</code> API</li> <li><a href="https://github.com/zloirock/core-js/commit/691125e5704ceebdb0318ae746227095871fb0e6"><code>691125e</code></a> add NodeJS 18.0 compat data</li> <li><a href="https://github.com/zloirock/core-js/commit/e4aa6262eaa6904ef086594d61c595fc23f2812a"><code>e4aa626</code></a> make tests work on NodeJS 18</li> <li><a href="https://github.com/zloirock/core-js/commit/6844ba3929bbd3dbf1efab82f941bf45f369b6a3"><code>6844ba3</code></a> update dependencies</li> <li><a href="https://github.com/zloirock/core-js/commit/a0f8ce1cd8244f818992bef25efeca27856abf54"><code>a0f8ce1</code></a> add NodeJS 18.0 compat data mapping</li> <li><a href="https://github.com/zloirock/core-js/commit/862f06a56d33e5db92ead8084d56f9b57934e88d"><code>862f06a</code></a> prevent crash with unexist <code>browser</code></li> <li><a href="https://github.com/zloirock/core-js/commit/2c3dcf08f64b4841d379587b2d57fbecd769de2e"><code>2c3dcf0</code></a> update dependencies</li> <li><a href="https://github.com/zloirock/core-js/commit/889643e8239736bf4b2f4735c202a6f51c6b4034"><code>889643e</code></a> improve some cases of <code>RegExp</code> flags handling</li> <li><a href="https://github.com/zloirock/core-js/commit/a9dc76937bb80c5ac4779fb7486ea3abcc94b0cb"><code>a9dc769</code></a> take into account <code>.hasIndices</code> regex flag</li> <li>Additional commits viewable in <a href="https://github.com/zloirock/core-js/compare/v3.20.2...v3.22.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=core-js&package-manager=npm_and_yarn&previous-version=3.20.2&new-version=3.22.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
arthur added the pull-request label 2025-12-01 17:06:31 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
arthur
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: arthur/website-old#255
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?