Update dependency core-js to v3.26.0

[renovate-config-app]

This PR contains the following updates:

Package	Type	Update	Change
core-js	dependencies	minor	3.21.1 -> 3.26.0

---

Release Notes

zloirock/core-js

v3.26.0

Compare Source

• Array.fromAsync proposal:
  • Moved to Stage 3, September TC39 meeting
  • Avoid observable side effects of %Array.prototype.values% usage in array-like branch, proposal-array-from-async/30
• Added well-formed unicode strings stage 2 proposal:
  • String.prototype.isWellFormed
  • String.prototype.toWellFormed
• Recent updates of the iterator helpers proposal:
  • Added a counter parameter to helpers, proposal-iterator-helpers/211
  • Don't await non-objects returned from functions passed to AsyncIterator helpers, proposal-iterator-helpers/239
  • { Iterator, AsyncIterator }.prototype.flatMap supports returning both - iterables and iterators, proposal-iterator-helpers/233
  • Early exit on broken .next in missed cases of { Iterator, AsyncIterator }.from, proposal-iterator-helpers/232
• Added self polyfill as a part of The Minimum Common Web Platform API, specification, #​1118
• Added inverse option to core-js-compat, #​1119
• Added format option to core-js-builder, #​1120
• Added NodeJS 19.0 compat data
• Added Deno 1.26 and 1.27 compat data
• Added Opera Android 72 compat data mapping
• Updated Electron 22 compat data mapping

v3.25.5

Compare Source

• Fixed regression with an error on reuse of some built-in methods from another realm, #​1133

v3.25.4

Compare Source

• Added a workaround of a Nashorn bug with Function.prototype.{ call, apply, bind } on string methods, #​1128
• Updated lists of [Serializable] and [Transferable] objects in the structuredClone polyfill. Mainly, for better error messages if polyfilling of cloning such types is impossible
• Array.prototype.{ group, groupToMap } marked as supported from V8 ~ Chromium 108
• Added Electron 22 compat data mapping

v3.25.3

Compare Source

• Forced polyfilling of Array.prototype.groupToMap in the pure version for returning wrapped Map instances
• Fixed existence of Array.prototype.{ findLast, findLastIndex } in /stage/4 entry
• Added Opera Android 71 compat data mapping
• Some stylistic changes

v3.25.2

Compare Source

• Considering document.all as a callable in some missed cases
• Added Safari 16.0 compat data
• Added iOS Safari 16.0 compat data mapping
• Fixed some ancient iOS Safari versions compat data mapping

v3.25.1

Compare Source

• Added some fixes and workarounds of FF30- typed arrays bug that does not properly convert objects to numbers
• Added sideEffects field to core-js-pure package.json for better tree shaking, #​1117
• Dropped semver dependency from core-js-compat
  • semver package (ironically) added a breaking change and dropped NodeJS 8 support in the minor 7.1 version, after that semver in core-js-compat was pinned to 7.0 since for avoiding breaking changes it should support NodeJS 8. However, since core-js-compat is usually used with other packages that use semver dependency, it causes multiple duplication of semver in dependencies. So I decided to remove semver dependency and replace it with a couple of simple helpers.
• Added Bun 0.1.6-0.1.11 compat data
• Added Deno 1.25 compat data mapping
• Updated Electron 21 compat data mapping
• Some stylistic changes, minor fixes, and improvements

v3.25.0

Compare Source

• Added Object.prototype.__proto__ polyfill
  • It's optional, legacy, and in some cases (mainly because of developers' mistakes) can cause problems, but some libraries depend on it, and most code can't work without the proper libraries' ecosystem
  • Only for modern engines where this feature is missed (like Deno), it's not installed in IE10- since here we have no proper way setting of the prototype
  • Without fixes of early implementations where it's not an accessor since those fixes are impossible
  • Only for the global version
• Considering document.all as an object in some missed cases, see ECMAScript Annex B 3.6
• Avoiding unnecessary promise creation and validation result in %WrapForValid(Async)IteratorPrototype%.return, proposal-iterator-helpers/215
• Fixed omitting the result of proxing .return in %IteratorHelperPrototype%.return, #​1116
• Fixed the order creation of properties of iteration result object of some iterators (value should be created before done)
• Fixed some cases of Safari < 13 bug - silent on non-writable array .length setting
• Fixed ArrayBuffer.length in V8 ~ Chrome 27-
• Relaxed condition of re-usage native WeakMap for internal states with multiple core-js copies
• Availability cloning of FileList in the structuredClone polyfill extended to some more old engines versions
• Some stylistic changes and minor fixes
• Throwing a TypeError in core-js-compat / core-js-builder in case of passing invalid module names / filters for avoiding unexpected result, related to #​1115
• Added missed NodeJS 13.2 to esmodules core-js-compat / core-js-builder target
• Added Electron 21 compat data mapping
• Added Oculus Browser 23.0 compat data mapping

v3.24.1

Compare Source

• NodeJS is ignored in IS_BROWSER detection to avoid a false positive with jsdom, #​1110
• Fixed detection of @@​species support in Promise in some old engines
• { Array, %TypedArray% }.prototype.{ findLast, findLastIndex } marked as shipped in FF104
• Added iOS Safari 15.6 compat data mapping
• Fixed Opera 15 compat data mapping

v3.24.0

Compare Source

• Recent updates of the iterator helpers proposal, #​1101:
  • .asIndexedPairs renamed to .indexed, proposal-iterator-helpers/183:
    • Iterator.prototype.asIndexedPairs -> Iterator.prototype.indexed
    • AsyncIterator.prototype.asIndexedPairs -> AsyncIterator.prototype.indexed
  • Avoid exposing spec fiction %AsyncFromSyncIteratorPrototype% in AsyncIterator.from and Iterator.prototype.toAsync, proposal-iterator-helpers/182, proposal-iterator-helpers/202
  • Avoid unnecessary promise creation in %WrapForValidAsyncIteratorPrototype%.next, proposal-iterator-helpers/197
  • Do not validate value in %WrapForValid(Async)IteratorPrototype%.next, proposal-iterator-helpers/197 and proposal-iterator-helpers/205
  • Do not forward the parameter of .next / .return to an underlying iterator by the extended iterator protocol, a part of proposal-iterator-helpers/194
  • .throw methods removed from all wrappers / helpers prototypes, a part of proposal-iterator-helpers/194
  • Close inner iterators of { Iterator, AsyncIterator }.prototype.flatMap proxy iterators on .return, proposal-iterator-helpers/195
  • Throw RangeError on NaN in { Iterator, AsyncIterator }.prototype.{ drop, take }, proposal-iterator-helpers/181
  • Many other updates and fixes of this proposal
• %TypedArray%.prototype.toSpliced method removed from the change array by copy proposal and marked as obsolete in core-js, proposal-change-array-by-copy/88
• Polyfill Promise with unhandledrejection event support (browser style) in Deno < 1.24
• Available new targets in core-js-compat / core-js-builder and added compat data for them:
  • Bun (bun), compat data for 0.1.1-0.1.5, #​1103
  • Hermes (hermes), compat data for 0.1-0.11, #​1099
  • Oculus Browser (oculus), compat data mapping for 3.0-22.0, #​1098
• Added Samsung Internet 18.0 compat data mapping

v3.23.5

Compare Source

• Fixed a typo in the structuredClone feature detection, #​1106
• Added Opera Android 70 compat data mapping

v3.23.4

Compare Source

• Added a workaround of the Bun ~ 0.1.1 bug that define some globals with incorrect property descriptors and that causes a crash of core-js
• Added a fix of the FF103+ structuredClone bugs (1774866 (fixed in FF104) and 1777321 (still not fixed)) that now can clone errors, but .stack of the clone is an empty string
• Fixed { Map, WeakMap }.prototype.emplace logic, #​1102
• Fixed order of errors throwing on iterator helpers

v3.23.3

Compare Source

• Changed the order of operations in %TypedArray%.prototype.toSpliced following proposal-change-array-by-copy/89
• Fixed regression of some IE8- issues

v3.23.2

Compare Source

• Avoided creation of extra properties for the handling of %TypedArray% constructors in new methods, #​1092 (comment)
• Added Deno 1.23 compat data mapping

v3.23.1

Compare Source

• Fixed possible error on multiple core-js copies, #​1091
• Added v flag to RegExp.prototype.flags implementation in case if current V8 bugs will not be fixed before this flag implementation

v3.23.0

Compare Source

• Array find from last moved to the stable ES, according to June 2022 TC39 meeting:
  • Array.prototype.findLast
  • Array.prototype.findLastIndex
  • %TypedArray%.prototype.findLast
  • %TypedArray%.prototype.findLastIndex
• Methods from the Array grouping proposal renamed, according to June 2022 TC39 meeting:
  • Array.prototype.groupBy -> Array.prototype.group
  • Array.prototype.groupByToMap -> Array.prototype.groupToMap
• Changed the order of operations in %TypedArray%.prototype.with following proposal-change-array-by-copy/86, according to June 2022 TC39 meeting
• Decorator Metadata proposal extracted from Decorators proposal as a separate stage 2 proposal, according to March 2022 TC39 meeting, Symbol.metadataKey replaces Symbol.metadata
• Added Array.prototype.push polyfill with some fixes for modern engines
• Added Array.prototype.unshift polyfill with some fixes for modern engines
• Fixed a bug in the order of getting flags in RegExp.prototype.flags in the actual version of V8
• Fixed property descriptors of some Math and Number constants
• Added a workaround of V8 ArrayBufferDetaching protector cell invalidation and performance degradation on structuredClone feature detection, one more case of #​679
• Added detection of NodeJS bug in structuredClone that can not clone DOMException (just in case for future versions that will fix other issues)
• Compat data:
  • Added NodeJS 18.3 compat data mapping
  • Added and fixed Deno 1.22 and 1.21 compat data mapping
  • Added Opera Android 69 compat data mapping
  • Updated Electron 20.0 compat data mapping

v3.22.8

Compare Source

• Fixed possible multiple call of ToBigInt / ToNumber conversion of the argument passed to %TypedArray%.prototype.fill in V8 ~ Chrome < 59, Safari < 14.1, FF < 55, Edge <=18
• Fixed some cases of DeletePropertyOrThrow in IE9-
• Fixed the kind of error (TypeError instead of Error) on incorrect exec result in RegExp.prototype.test polyfill
• Fixed dependencies of { actual, full, features }/typed-array/at entries
• Added Electron 20.0 compat data mapping
• Added iOS Safari 15.5 compat data mapping
• Refactoring

v3.22.7

Compare Source

• Added a workaround for V8 ~ Chrome 53 bug with non-writable prototype of some methods, #​1083

v3.22.6

Compare Source

• Fixed possible double call of ToNumber conversion on arguments of Math.{ fround, trunc } polyfills
• Array.prototype.includes marked as fixed in FF102

v3.22.5

Compare Source

• Ensured that polyfilled constructors .prototype is non-writable
• Ensured that polyfilled methods .prototype is not defined
• Added detection and fix of a V8 ~ Chrome <103 bug of struturedClone that returns null if cloned object contains multiple references to one error

v3.22.4

Compare Source

• Ensured proper .length of polyfilled functions even in compressed code (excepting some ancient engines)
• Ensured proper .name of polyfilled accessors (excepting some ancient engines)
• Ensured proper source / ToString conversion of polyfilled accessors
• Actualized Rhino compat data
• Refactoring

v3.22.3

Compare Source

• Added a fix for FF99+ Array.prototype.includes broken on sparse arrays

v3.22.2

Compare Source

• Fixed URLSearchParams in IE8- that was broken in the previous release
• Fixed __lookupGetter__ entries

v3.22.1

Compare Source

• Improved some cases of RegExp flags handling
• Prevented experimental warning in NodeJS ~ 18.0 on detection fetch API
• Added NodeJS 18.0 compat data

v3.22.0

Compare Source

• 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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Renovate Bot.

[renovate-config-app]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular-devkit/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/tslint
npm ERR!   dev tslint@"5.20.1" from the root project
npm ERR!   peer tslint@"^5.0.0 || ^6.0.0" from [email protected]
npm ERR!   node_modules/codelyzer
npm ERR!     dev codelyzer@"6.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional tslint@"^6.1.0" from @angular-devkit/[email protected]
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"12.2.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/tslint
npm ERR!   peerOptional tslint@"^6.1.0" from @angular-devkit/[email protected]
npm ERR!   node_modules/@angular-devkit/build-angular
npm ERR!     dev @angular-devkit/build-angular@"12.2.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2022-10-26T04_59_23_586Z-debug-0.log