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.
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
Dependabot commands
You can trigger Dependabot actions by commenting on this MR
$dependabot rebase will rebase this MR
$dependabot recreate will recreate this MR rewriting all the manual changes and resolving conflicts
Bumps [core-js](https://github.com/zloirock/core-js) from 3.21.1 to 3.22.0.
<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.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.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.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 <17.9 <code>atob</code> does not ignore spaces, <a href="https://github.com/nodejs/node/issues/42530">node/42530</a></li>
<li>Actual NodeJS <code>atob</code> does not validate encoding, <a href="https://github.com/nodejs/node/issues/42646">node/42646</a></li>
<li>FF26- implementation does not properly convert argument to string</li>
<li>IE / Edge <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.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.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> -> <code>core-js-builder</code> -> <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>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/zloirock/core-js/commit/c5e56b664756455f9715481eca92f4a3a421f475"><code>c5e56b6</code></a> 3.22.0</li>
<li><a href="https://github.com/zloirock/core-js/commit/01b057cd217415a8dc26ab6c3fb3319fc403cc45"><code>01b057c</code></a> update entries in the readme</li>
<li><a href="https://github.com/zloirock/core-js/commit/06c6a566c7f07420fbd78553bc273eb5834d0597"><code>06c6a56</code></a> use <code>import</code> in some examples</li>
<li><a href="https://github.com/zloirock/core-js/commit/0f3c6031ed9de3ade3078f57883a68c4300bf9e7"><code>0f3c603</code></a> avoid propagation of removed parts of proposals to upper stages</li>
<li><a href="https://github.com/zloirock/core-js/commit/24d2e5dde76418094df5d9a8799c58104caf093a"><code>24d2e5d</code></a> drop splitted / renamed modules from <code>modules-by-versions</code></li>
<li><a href="https://github.com/zloirock/core-js/commit/8c91babc67e269a6fbb19325446dea9a0cfc3aef"><code>8c91bab</code></a> update dependencies</li>
<li><a href="https://github.com/zloirock/core-js/commit/1e07b0c00b5a92037c2c309205842701f428983c"><code>1e07b0c</code></a> add<code>get-modules-list-for-target-version</code> tests</li>
<li><a href="https://github.com/zloirock/core-js/commit/eff765f2198cecc07bfe34bce10ef32b94dc8b50"><code>eff765f</code></a> disable forced replacement for methods from "Change <code>Array</code> by copy" proposal</li>
<li><a href="https://github.com/zloirock/core-js/commit/a7aab7f10ba7fc84e6d7f817b0dad71de9b84dc3"><code>a7aab7f</code></a> use <code>import</code> instead of <code>require</code></li>
<li><a href="https://github.com/zloirock/core-js/commit/7717637d66fdf2870a1aabb3b4a84459f5b48ed1"><code>7717637</code></a> add some tests</li>
<li>Additional commits viewable in <a href="https://github.com/zloirock/core-js/compare/v3.21.1...v3.22.0">compare view</a></li>
</ul>
</details>
<br />
---
<details>
<summary>Dependabot commands</summary>
<br />
You can trigger Dependabot actions by commenting on this MR
- `$dependabot rebase` will rebase this MR
- `$dependabot recreate` will recreate this MR rewriting all the manual changes and resolving conflicts
</details>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Bumps core-js from 3.21.1 to 3.22.0.
Changelog
Sourced from core-js's changelog.
Commits
c5e56b63.22.001b057cupdate entries in the readme06c6a56useimportin some examples0f3c603avoid propagation of removed parts of proposals to upper stages24d2e5ddrop splitted / renamed modules frommodules-by-versions8c91babupdate dependencies1e07b0caddget-modules-list-for-target-versiontestseff765fdisable forced replacement for methods from "ChangeArrayby copy" proposala7aab7fuseimportinstead ofrequire7717637add some testsDependabot commands
You can trigger Dependabot actions by commenting on this MR
$dependabot rebasewill rebase this MR$dependabot recreatewill recreate this MR rewriting all the manual changes and resolving conflictsmentioned in commit
10507d8012