patch: Update dependency core-js to ^3.27.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
core-js	^3.18.3 -> ^3.27.1

---

Release Notes

zloirock/core-js

v3.27.1

Compare Source

• Fixed a Chakra-based MS Edge (18-) bug that unfreeze (O_o) frozen arrays used as WeakMap keys
• Fixing of the previous bug also fixes some cases of String.dedent in MS Edge
• Fixed dependencies of some entries

v3.27.0

Compare Source

• Iterator Helpers proposal:
  • Built-ins:
    • Iterator
      • Iterator.from
      • Iterator.prototype.drop
      • Iterator.prototype.every
      • Iterator.prototype.filter
      • Iterator.prototype.find
      • Iterator.prototype.flatMap
      • Iterator.prototype.forEach
      • Iterator.prototype.map
      • Iterator.prototype.reduce
      • Iterator.prototype.some
      • Iterator.prototype.take
      • Iterator.prototype.toArray
      • Iterator.prototype.toAsync
      • Iterator.prototype[@​@​toStringTag]
    • AsyncIterator
      • AsyncIterator.from
      • AsyncIterator.prototype.drop
      • AsyncIterator.prototype.every
      • AsyncIterator.prototype.filter
      • AsyncIterator.prototype.find
      • AsyncIterator.prototype.flatMap
      • AsyncIterator.prototype.forEach
      • AsyncIterator.prototype.map
      • AsyncIterator.prototype.reduce
      • AsyncIterator.prototype.some
      • AsyncIterator.prototype.take
      • AsyncIterator.prototype.toArray
      • AsyncIterator.prototype[@​@​toStringTag]
  • Moved to Stage 3, November 2022 TC39 meeting
  • Added /actual/ entries, unconditional forced replacement disabled for features that survived to Stage 3
  • .from accept strings, .flatMap throws on strings returned from the callback, proposal-iterator-helpers/244, proposal-iterator-helpers/250
  • .from and .flatMap throws on non-object iterators, proposal-iterator-helpers/253
• Set methods proposal:
  • Built-ins:
    • Set.prototype.intersection
    • Set.prototype.union
    • Set.prototype.difference
    • Set.prototype.symmetricDifference
    • Set.prototype.isSubsetOf
    • Set.prototype.isSupersetOf
    • Set.prototype.isDisjointFrom
  • Moved to Stage 3, November 2022 TC39 meeting
  • Reimplemented with new semantics:
    • Optimized performance (iteration over lowest set)
    • Accepted only Set-like objects as an argument, not all iterables
    • Accepted only Sets as this, no @@​species support, and other minor changes
  • Added /actual/ entries, unconditional forced replacement changed to feature detection
  • For avoiding breaking changes:
    • New versions of methods are implemented as new modules and available in new entries or entries where old versions of methods were not available before (like /actual/ namespace)
    • In entries where they were available before (like /full/ namespace), those methods are available with fallbacks to old semantics (in addition to Set-like, they accept iterable objects). This behavior will be removed from the next major release
• Well-Formed Unicode Strings proposal:
  • Methods:
    • String.prototype.isWellFormed
    • String.prototype.toWellFormed
  • Moved to Stage 3, November 2022 TC39 meeting
  • Added /actual/ entries, disabled unconditional forced replacement
• Explicit resource management Stage 3 and Async explicit resource management Stage 2 proposals:
  • Renamed from "using statement" and splitted into 2 (sync and async) proposals
  • In addition to already present well-known symbols, added new built-ins:
    • Symbol.dispose
    • Symbol.asyncDispose
    • SuppressedError
    • DisposableStack
      • DisposableStack.prototype.dispose
      • DisposableStack.prototype.use
      • DisposableStack.prototype.adopt
      • DisposableStack.prototype.defer
      • DisposableStack.prototype.move
      • DisposableStack.prototype[@​@​dispose]
    • AsyncDisposableStack
      • AsyncDisposableStack.prototype.disposeAsync
      • AsyncDisposableStack.prototype.use
      • AsyncDisposableStack.prototype.adopt
      • AsyncDisposableStack.prototype.defer
      • AsyncDisposableStack.prototype.move
      • AsyncDisposableStack.prototype[@​@​asyncDispose]
    • Iterator.prototype[@​@​dispose]
    • AsyncIterator.prototype[@​@​asyncDispose]
  • Sync version of this proposal moved to Stage 3, November 2022 TC39 meeting
  • Added /actual/ namespace entries for Stage 3 proposal
• Added String.dedent stage 2 proposal
  • Method String.dedent
  • Throws an error on non-frozen raw templates for avoiding possible breaking changes in the future, proposal-string-dedent/75
• Compat data targets improvements:
  • React Native from 0.70 shipped with Hermes as the default engine. However, bundled Hermes versions differ from standalone Hermes releases. So added react-native target for React Native with bundled Hermes.
  • According to the documentation, Oculus Browser was renamed to Meta Quest Browser, so oculus target was renamed to quest.
  • opera_mobile target name is confusing since it contains data for the Chromium-based Android version, but iOS Opera is Safari-based. So opera_mobile target was renamed to opera-android.
  • android target name is also confusing for someone - that means Android WebView, some think thinks that it's Chrome for Android, but they have some differences. For avoiding confusion, added chrome-android target.
  • For consistency with two previous cases, added firefox-android target.
  • For avoiding breaking changes, the oculus and opera_mobile fields are available in the compat data till the next major release.
• Compat data improvements:
  • Array.fromAsync marked as supported from Bun 0.3.0
  • String.prototype.{ isWellFormed, toWellFormed } marked as supported from Bun 0.4.0
  • Change Array by copy proposal marked as supported from Deno 1.27, deno/16429
  • Added Deno 1.28 / 1.29 compat data mapping
  • Added NodeJS 19.2 compat data mapping
  • Added Samsung Internet 19.0 compat data mapping
  • Added Quest Browser 24.0 compat data mapping
  • Fixed the first version in the Chromium-based Edge compat data mapping
• { Map, WeakMap }.prototype.emplace became stricter by the spec draft
• Smoothed behavior of some conflicting proposals
• Removed some generic behavior (like @@​species pattern) of some .prototype methods from the new collections methods proposal and the Array deduplication proposal that most likely will not be implemented since it contradicts the current TC39 policy
• Added pure version of the Number constructor, #​1154, #​1155, thanks @​trosos
• Added set(Timeout|Interval|Immediate) extra arguments fix for Bun 0.3.0- (similarly to IE9-), bun/1633
• Fixed handling of sparse arrays in structuredClone, #​1156
• Fixed a theoretically possible future conflict of polyfills definitions in the pure version
• Some refactoring and optimization

v3.26.1

Compare Source

• Disabled forced replacing of Array.fromAsync since it's on Stage 3
• Avoiding a check of the target in the internal function-uncurry-this helper where it's not required - minor optimization and preventing problems in some broken environments, a workaround of #​1141
• V8 will not ship Array.prototype.{ group, groupToMap } in V8 ~ Chromium 108, proposal-array-grouping/44

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

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.