chore(deps): update dependency core-js to v3.36.1 #7

renovate · 2021-10-12T12:17:06Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
core-js (source)	`3.12.1` -> `3.36.1`

Release Notes

zloirock/core-js (core-js)

`v3.36.1`

Compare Source

Changes v3.36.0...v3.36.1
Fixed some validation cases in Object.setPrototypeOf, #1329, thanks @minseok-choe
Fixed the order of validations in Array.from, #1331, thanks @minseok-choe
Added a fix of Bun queueMicrotask arity
Added a fix of Bun URL.canParse arity
Added a fix of Bun SuppressedError extra arguments support and arity
Compat data improvements:
- value argument of URLSearchParams.prototype.{ has, delete } marked as supported from Bun 1.0.31
- Added React Native 0.74 Hermes compat data, Array.prototype.{ toSpliced, toReversed, with } and atob marked as supported
- Added Deno 1.41.3 compat data mapping
- Added Opera Android 81 compat data mapping
- Added Samsung Internet 25 compat data mapping
- Added Oculus Quest Browser 32 compat data mapping
- Updated Electron 30 compat data mapping

`v3.36.0`

Compare Source

ArrayBuffer.prototype.transfer and friends proposal:
- Built-ins:
  - ArrayBuffer.prototype.detached
  - ArrayBuffer.prototype.transfer
  - ArrayBuffer.prototype.transferToFixedLength
- Moved to stable ES, Febrary 2024 TC39 meeting
- Added es. namespace modules, /es/ and /stable/ namespaces entries
Uint8Array to / from base64 and hex proposal:
- Methods:
  - Uint8Array.fromBase64
  - Uint8Array.fromHex
  - Uint8Array.prototype.toBase64
  - Uint8Array.prototype.toHex
- Moved to stage 3, Febrary 2024 TC39 meeting
- Added /actual/ namespace entries
- Skipped adding new methods of writing to existing arrays to clarification some moments
Promise.try proposal has been resurrected and moved to stage 2, Febrary 2024 TC39 meeting
Added an entry point for the new TC39 proposals stage - core-js/stage/2.7 - still empty
Fixed regression in Set.prototype.intersection feature detection
Fixed a missed check in Array.prototype.{ indexOf, lastIndexOf, includes }, #1325, thanks @minseok-choe
Fixed a missed check in Array.prototype.{ reduce, reduceRight }, #1327, thanks @minseok-choe
Fixed Array.from and some other methods with proxy targets, #1322, thanks @minseok-choe
Fixed dependencies loading for modules from ArrayBuffer.prototype.transfer and friends proposal in some specific cases in IE10-
Dropped context workaround from collection static methods entries since with current methods semantic it's no longer required
Added instance methods polyfills to entries of collections static methods that produce collection instances
Added missed Date.prototype.toJSON to JSON.stringify entries dependencies
Added debugging info in some missed cases
Compat data improvements:
- { Map, Object }.groupBy, Promise.withResolvers, ArrayBuffer.prototype.transfer and friends marked as supported from Safari 17.4
- New Set methods fixed and marked as supported from V8 ~ Chrome 123
- Added Deno 1.40 compat data mapping
- Symbol.metadata marked as supported from Deno 1.40.4
- Updated Electron 30 compat data mapping

`v3.35.1`

Compare Source

Fixed internal ToLength operation with bigints, #1318
Removed significant redundant code from String#split polyfill
Fixed setting names of methods with symbol keys in some old engines
Minor fix of prototype methods export logic in the pure version
Compat data improvements:
- Iterator helpers proposal methods marked as supported from V8 ~ Chrome 122
- Note that V8 ~ Chrome 122 add Set methods, but they have a bug similar to Safari
- self marked as fixed from Bun 1.0.22
- SuppressedError and Symbol.{ dispose , asyncDispose } marked as supported from Bun 1.0.23
- Added Oculus Quest Browser 31 compat data mapping
- Updated Electron 29 and added Electron 30 compat data mapping

`v3.35.0`

Compare Source

{ Map, Set, WeakMap, WeakSet }.{ from, of } became non-generic, following this and some other notes. Now they can be invoked without this, but no longer return subclass instances
Fixed handling some cases of non-enumerable symbol keys from Symbol polyfill
Removed unneeded NodeJS domains-related logic from queueMicrotask polyfill
Fixed subclassing of wrapped ArrayBuffer
Refactoring, many different minor optimizations
Compat data improvements:
- Array.fromAsync marked as supported from V8 ~ Chrome 121
- It seems that the ancient Array.prototype.push bug is fixed in V8 ~ Chrome 122 (Hallelujah!)
- ArrayBuffer.prototype.transfer and friends proposal features marked as supported from FF 122 and Bun 1.0.19
- Object.groupBy and Map.groupBy marked as supported from Bun 1.0.19
- Since Iterator helpers proposal methods are still not disabled in Deno, the web compatibility issue why it was disabled in Chromium makes no sense for Deno and fixed in the spec, they marked as supported from Deno 1.37
- Added Opera Android 80 and updated Opera Android 79 compat data mapping
- Added Samsung Internet 24 compat data mapping

`v3.34.0`

Compare Source

Array grouping proposal:
- Methods:
  - Object.groupBy
  - Map.groupBy
- Moved to stable ES, November 2023 TC39 meeting
- Added es. namespace modules, /es/ and /stable/ namespaces entries
Promise.withResolvers proposal:
- Method:
  - Promise.withResolvers
- Moved to stable ES, November 2023 TC39 meeting
- Added es. namespace module, /es/ and /stable/ namespaces entries
Fixed a web incompatibility issue of Iterator helpers proposal, proposal-iterator-helpers/287 and some following changes, November 2023 TC39 meeting
Added Uint8Array to / from base64 and hex stage 2 proposal:
- Methods:
  - Uint8Array.fromBase64
  - Uint8Array.fromHex
  - Uint8Array.prototype.toBase64
  - Uint8Array.prototype.toHex
Relaxed some specific cases of Number.fromString validation before clarification of proposal-number-fromstring/24
Fixed @@toStringTag property descriptors on DOM collections, #1312
Fixed the order of arguments validation in Array iteration methods, #1313
Some minor atob / btoa improvements
Compat data improvements:
- Promise.withResolvers marked as shipped from FF121

`v3.33.3`

Compare Source

Fixed an issue getting the global object on Duktape, #1303
Avoid sharing internal [[DedentMap]] from String.dedent proposal between core-js instances before stabilization of the proposal
Some internal untangling
Compat data improvements:
- Added Deno 1.38 compat data mapping
- Array.fromAsync marked as supported from Deno 1.38
- Symbol.{ dispose, asyncDispose } marked as supported from Deno 1.38
- Added Opera Android 79 compat data mapping
- Added Oculus Quest Browser 30 compat data mapping
- Updated Electron 28 and 29 compat data mapping

`v3.33.2`

Compare Source

Simplified structuredClone polyfill, avoided second tree pass in cases of transferring
Added support of SuppressedError to structuredClone polyfill
Removed unspecified unnecessary ArrayBuffer and DataView dependencies of structuredClone lack of which could cause errors in some entries in IE10-
Fixed handling of fractional number part in Number.fromString
Compat data improvements:
- URL.canParse marked as supported from Chromium 120
- Updated Opera Android 78 compat data mapping
- Added Electron 29 compat data mapping

`v3.33.1`

Compare Source

Added one more workaround of possible error with Symbol polyfill on global object, #1289
Directly specified type: commonjs in package.json of all packages to avoid potential breakage in future Node versions, see this issue
Prevented potential issue with lack of some dependencies after automatic optimization polyfills of some methods in the pure version
Some minor internal fixes and optimizations
Compat data improvements:
- String.prototype.{ isWellFormed, toWellFormed } marked as supported from FF119
- Added React Native 0.73 Hermes compat data, mainly fixes of some issues
- Added NodeJS 21.0 compat data mapping

`v3.33.0`

Compare Source

Re-introduced RegExp escaping stage 2 proposal, September 2023 TC39 meeting:
- Added RegExp.escape method with the new set of symbols for escaping
- Some years ago, it was presented in core-js, but it was removed after rejecting the old version of this proposal
Added ArrayBuffer.prototype.{ transfer, transferToFixedLength } and support transferring of ArrayBuffers via structuredClone to engines with MessageChannel
Optimized Math.f16round polyfill
Fixed some conversion cases of Math.f16round and DataView.prototype.{ getFloat16, setFloat16 }
Fully forced polyfilling of the TC39 Observable proposal because of incompatibility with the new WHATWG Observable proposal
Added an extra workaround of errors with exotic environment objects in Symbol polyfill, #1289
Some minor fixes and stylistic changes
Compat data improvements:
- V8 unshipped Iterator helpers because of some Web compatibility issues
- Promise.withResolvers marked as supported from V8 ~ Chrome 119
- Array grouping proposal features marked as supported from FF119
- value argument of URLSearchParams.prototype.{ has, delete } marked as properly supported from V8 ~ Chrome 118
- URL.canParse and URLSearchParams.prototype.size marked as supported from Bun 1.0.2
- Added Deno 1.37 compat data mapping
- Added Electron 28 compat data mapping
- Added Opera Android 78 compat data mapping

`v3.32.2`

Compare Source

Fixed structuredClone feature detection [email protected] bug, #1288
Added a workaround of old WebKit + eval bug, #1287
Compat data improvements:
- Added Samsung Internet 23 compat data mapping
- Added Quest Browser 29 compat data mapping

`v3.32.1`

Compare Source

Fixed some cases of IEEE754 rounding, #1279, thanks @petamoriken
Prevented injection process polyfill to core-js via some bundlers or esm.sh, #1277
Some minor fixes and stylistic changes
Compat data improvements:
- Promise.withResolvers marked as supported from Bun 0.7.1
- Added Opera Android 77 compat data mapping
- Updated Electron 27 compat data mapping

`v3.32.0`

Compare Source

Array grouping proposal, July 2023 TC39 meeting updates:
- Moved back to stage 3
- Added /actual/ namespaces entries, unconditional forced replacement changed to feature detection
Promise.withResolvers proposal, July 2023 TC39 meeting updates:
- Moved to stage 3
- Added /actual/ namespaces entries, unconditional forced replacement changed to feature detection
Set methods stage 3 proposal, July 2023 TC39 meeting updates:
- Throw on negative Set sizes, proposal-set-methods/88
- Removed IsCallable check in GetKeysIterator, proposal-set-methods/101
Iterator Helpers stage 3 proposal:
- Avoid creating observable String wrapper objects, July 2023 TC39 meeting update, proposal-iterator-helpers/281
- Iterator is not constructible from the active function object (works as an abstract class)
Async explicit resource management:
- Moved back into the initial proposal -> moved to stage 3, proposal-explicit-resource-management/154
- Added /actual/ namespace entries, unconditional forced replacement changed to feature detection
- Ignore return value of [@@dispose]() method when hint is async-dispose, proposal-explicit-resource-management/180
- Added ticks for empty resources, proposal-explicit-resource-management/163
Added some methods from Float16Array stage 3 proposal:
- There are some reason why I don't want to add Float16Array right now, however, make sense to add some methods from this proposal.
- Methods:
  - Math.f16round
  - DataView.prototype.getFloat16
  - DataView.prototype.setFloat16
Added DataView get / set Uint8Clamped methods stage 1 proposal:
- Methods:
  - DataView.prototype.getUint8Clamped
  - DataView.prototype.setUint8Clamped
Used strict mode in some missed cases, #1269
Fixed a Chromium 117 bug in value argument of URLSearchParams.prototype.{ has, delete }
Fixed early WebKit ~ Safari 17.0 beta Set methods implementation by the actual spec
Fixed incorrect Symbol.{ dispose, asyncDispose } descriptors from NodeJS 20.4 / transpilers helpers / userland code
Fixed forced polyfilling of some iterator helpers that should return wrapped iterator in the pure version
Fixed and exposed AsyncIteratorPrototype core-js/configurator option, #1268
Compat data improvements:
- Sync Iterator helpers proposal features marked as supported from V8 ~ Chrome 117
- Array grouping proposal features marked as supported from V8 ~ Chrome 117
- Mark Symbol.{ dispose, asyncDispose } as supported from NodeJS 20.5.0 (as mentioned above, NodeJS 20.4.0 add it, but with incorrect descriptors)
- Added Electron 27 compat data mapping

`v3.31.1`

Compare Source

Fixed a structuredClone bug with cloning views of transferred buffers, #1265
Fixed the order of arguments validation in DataView methods
Allowed cloning of Float16Array in structuredClone
Compat data improvements:
- Set methods proposal marked as supported from Safari 17.0
- New URL features: URL.canParse, URLSearchParams.prototype.size and value argument of URLSearchParams.prototype.{ has, delete } marked as supported from Safari 17.0
- value argument of URLSearchParams.prototype.{ has, delete } marked as supported from Deno 1.35
- AggregateError and well-formed JSON.stringify marked as supported React Native 0.72 Hermes
- Added Deno 1.35 compat data mapping
- Added Quest Browser 28 compat data mapping
- Added missing NodeJS 12.16-12.22 compat data mapping
- Updated Opera Android 76 compat data mapping

`v3.31.0`

Compare Source

Well-formed unicode strings proposal:
- Methods:
  - String.prototype.isWellFormed method
  - String.prototype.toWellFormed method
- Moved to stable ES, May 2023 TC39 meeting
- Added es. namespace modules, /es/ and /stable/ namespaces entries
Array grouping proposal, May 2023 TC39 meeting updates:
- Because of the web compat issue, moved from prototype to static methods. Added:
  - Object.groupBy method
  - Map.groupBy method (with the actual semantic - with a minor difference it was present in the collections methods stage 1 proposal)
- Demoted to stage 2
Decorator Metadata proposal, May 2023 TC39 meeting updates:
- Moved to stage 3
- Added Function.prototype[Symbol.metadata] (=== null)
- Added /actual/ entries
Iterator Helpers stage 3 proposal:
- Changed Symbol.iterator fallback from callable check to undefined / null check, May 2023 TC39 meeting, proposal-iterator-helpers/272
- Removed IsCallable check on NextMethod, deferring errors to Call site, May 2023 TC39 meeting, proposal-iterator-helpers/274
Added Promise.withResolvers stage 2 proposal:
- Promise.withResolvers method
Symbol predicates stage 2 proposal:
- The methods renamed to end with Symbol, May 2023 TC39 meeting:
  - Symbol.isRegistered -> Symbol.isRegisteredSymbol method
  - Symbol.isWellKnown -> Symbol.isWellKnownSymbol method
Added value argument of URLSearchParams.prototype.{ has, delete }, url/735
Fixed some cases of increasing buffer size in ArrayBuffer.prototype.{ transfer, transferToFixedLength } polyfills
Fixed awaiting async AsyncDisposableStack.prototype.adopt callback, #1258
Fixed URLSearchParams#size in ES3 engines (IE8-)
Added a workaround in Object.{ entries, values } for some IE versions bug with invisible integer keys on null-prototype objects
Added TypeScript definitions to core-js-compat, #1235, thanks @susnux
Compat data improvements:
- Set.prototype.difference that was missed in Bun because of a bug added in 0.6.0
- Array.prototype.{ group, groupToMap } marked as no longer supported in WebKit runtimes because of the mentioned above web compat issue. For example, it's disabled from Bun 0.6.2
- Methods from the change Array by copy proposal marked as supported from FF115
- Array.fromAsync marked as supported from FF115
- URL.canParse marked as supported from FF115
- value argument of URLSearchParams.prototype.{ has, delete } marked as supported from NodeJS 20.2.0 and FF115
- Added Deno 1.34 compat data mapping
- Added Electron 26 compat data mapping
- Added Samsung Internet 22 compat data mapping
- Added Opera Android 75 and 76 compat data mapping
- Added Quest Browser 27 compat data mapping

`v3.30.2`

Compare Source

Added a fix for a NodeJS 20.0.0 bug with cloning File via structuredClone
Added protection from Terser unsafe String optimization, #1242
Added a workaround for getting proper global object in Figma plugins, #1231
Compat data improvements:
- Added NodeJS 20.0 compat data mapping
- Added Deno 1.33 compat data mapping
- URL.canParse marked as supported (fixed) from NodeJS 20.1.0 and Deno 1.33.2

`v3.30.1`

Compare Source

Added a fix for a NodeJS 19.9.0 URL.canParse bug
Compat data improvements:
- JSON.parse source text access proposal features marked as supported from V8 ~ Chrome 114
- ArrayBuffer.prototype.transfer and friends proposal features marked as supported from V8 ~ Chrome 114
- URLSearchParams.prototype.size marked as supported from V8 ~ Chrome 113

`v3.30.0`

Compare Source

Added URL.canParse method, url/763
Set methods proposal:
- Removed sort from Set.prototype.intersection, March 2023 TC39 meeting, proposal-set-methods/94
Iterator Helpers proposals (sync, async):
- Validate arguments before opening iterator, March 2023 TC39 meeting, proposal-iterator-helpers/265
Explicit Resource Management proposals (sync, async):
- (Async)DisposableStack.prototype.move marks the original stack as disposed, #1226
- Some simplifications like proposal-explicit-resource-management/150
Iterator.range proposal:
- Moved to Stage 2, March 2023 TC39 meeting
Decorator Metadata proposal:
- Returned to usage Symbol.metadata, March 2023 TC39 meeting, proposal-decorator-metadata/12
Compat data improvements:
- URLSearchParams.prototype.size marked as supported from FF112, NodeJS 19.8 and Deno 1.32
- Added Safari 16.4 compat data
- Added Deno 1.32 compat data mapping
- Added Electron 25 and updated 24 compat data mapping
- Added Samsung Internet 21 compat data mapping
- Added Quest Browser 26 compat data mapping
- Updated Opera Android 74 compat data

`v3.29.1`

Compare Source

Fixed dependencies of some entries
Fixed ToString conversion / built-ins nature of some accessors
String.prototype.{ isWellFormed, toWellFormed } marked as supported from V8 ~ Chrome 111
Added Opera Android 74 compat data mapping

`v3.29.0`

Compare Source

Added URLSearchParams.prototype.size getter, url/734
Allowed cloning resizable ArrayBuffers in the structuredClone polyfill
Fixed wrong export in /(stable|actual|full)/instance/unshift entries, #1207
Compat data improvements:
- Set methods proposal marked as supported from Bun 0.5.7
- String.prototype.toWellFormed marked as fixed from Bun 0.5.7
- Added Deno 1.31 compat data mapping

`v3.28.0`

Compare Source

3.28.0 - 2023.02.14

`v3.27.2`

Compare Source

Set methods proposal updates:
- Closing of iterators of Set-like objects on early exit, proposal-set-methods/85
- Some other minor internal changes
Added one more workaround of a webpack dev server bug on IE global methods, #1161
Fixed possible String.{ raw, cooked } error with empty template array
Used non-standard V8 Error.captureStackTrace instead of stack parsing in new error classes / wrappers where it's possible
Added detection correctness of iteration to Promise.{ allSettled, any } feature detection, Hermes issue
Compat data improvements:
- Change Array by copy proposal marked as supported from V8 ~ Chrome 110
- Added Samsung Internet 20 compat data mapping
- Added Quest Browser 25 compat data mapping
- Added React Native 0.71 Hermes compat data
- Added Electron 23 and 24 compat data mapping
- self marked as fixed in Deno 1.29.3, deno/17362
Minor tweaks of minification settings for core-js-bundle
Refactoring, some minor fixes, improvements, optimizations

`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 split 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%.pr

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.

renovate bot force-pushed the renovate/core-js-3.x branch from a0efdbd to 8998544 Compare October 12, 2021 19:58

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.18.2~~ chore(deps): update dependency core-js to v3.18.3 Oct 12, 2021

renovate bot force-pushed the renovate/core-js-3.x branch from 8998544 to 70edc66 Compare October 25, 2021 06:33

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.18.3~~ chore(deps): update dependency core-js to v3.19.0 Oct 25, 2021

renovate bot force-pushed the renovate/core-js-3.x branch from 70edc66 to 79717d6 Compare November 2, 2021 20:24

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.19.0~~ chore(deps): update dependency core-js to v3.19.1 Nov 2, 2021

renovate bot force-pushed the renovate/core-js-3.x branch from 79717d6 to bd4dc5a Compare November 29, 2021 19:00

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.19.1~~ chore(deps): update dependency core-js to v3.19.2 Nov 29, 2021

renovate bot force-pushed the renovate/core-js-3.x branch from bd4dc5a to 8fda478 Compare March 7, 2022 18:01

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.19.2~~ chore(deps): update dependency core-js to v3.21.1 Mar 7, 2022

renovate bot force-pushed the renovate/core-js-3.x branch from 8fda478 to 3adf538 Compare April 24, 2022 21:50

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.21.1~~ chore(deps): update dependency core-js to v3.22.2 Apr 24, 2022

renovate bot force-pushed the renovate/core-js-3.x branch from 3adf538 to 308653c Compare May 15, 2022 19:54

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.22.2~~ chore(deps): update dependency core-js to v3.22.5 May 15, 2022

renovate bot force-pushed the renovate/core-js-3.x branch from 308653c to 650238b Compare June 18, 2022 20:14

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.22.5~~ chore(deps): update dependency core-js to v3.23.1 Jun 18, 2022

renovate bot force-pushed the renovate/core-js-3.x branch from 650238b to e052bd9 Compare June 23, 2022 19:18

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.23.1~~ chore(deps): update dependency core-js to v3.23.2 Jun 23, 2022

renovate bot force-pushed the renovate/core-js-3.x branch from e052bd9 to 551736e Compare September 25, 2022 20:13

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.23.2~~ chore(deps): update dependency core-js to v3.25.2 Sep 25, 2022

renovate bot force-pushed the renovate/core-js-3.x branch from 551736e to fc5662f Compare March 18, 2023 00:07

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.25.2~~ chore(deps): update dependency core-js to v3.29.1 Mar 18, 2023

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.29.1~~ chore(deps): update dependency core-js to v3.30.2 May 28, 2023

renovate bot force-pushed the renovate/core-js-3.x branch from fc5662f to 6752004 Compare May 28, 2023 15:51

renovate bot force-pushed the renovate/core-js-3.x branch from 6752004 to ff19981 Compare June 12, 2023 23:47

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.30.2~~ chore(deps): update dependency core-js to v3.31.0 Jun 12, 2023

renovate bot force-pushed the renovate/core-js-3.x branch from ff19981 to eed08e5 Compare July 6, 2023 02:34

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.31.0~~ chore(deps): update dependency core-js to v3.31.1 Jul 6, 2023

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.31.1~~ chore(deps): update dependency core-js to v3.32.0 Jul 28, 2023

renovate bot force-pushed the renovate/core-js-3.x branch from eed08e5 to 57c0f1d Compare July 28, 2023 08:45

renovate bot force-pushed the renovate/core-js-3.x branch from 57c0f1d to 3bc99bb Compare August 19, 2023 02:59

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.32.0~~ chore(deps): update dependency core-js to v3.32.1 Aug 19, 2023

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.32.1~~ chore(deps): update dependency core-js to v3.32.2 Sep 8, 2023

renovate bot force-pushed the renovate/core-js-3.x branch from 3bc99bb to 9410bab Compare September 8, 2023 02:30

renovate bot force-pushed the renovate/core-js-3.x branch from 9410bab to 7a83918 Compare October 2, 2023 05:44

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.32.2~~ chore(deps): update dependency core-js to v3.33.0 Oct 2, 2023

renovate bot force-pushed the renovate/core-js-3.x branch from 7a83918 to 030da3d Compare October 21, 2023 11:28

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.33.0~~ chore(deps): update dependency core-js to v3.33.1 Oct 21, 2023

renovate bot force-pushed the renovate/core-js-3.x branch from 030da3d to d38b0ee Compare October 31, 2023 05:25

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.33.1~~ chore(deps): update dependency core-js to v3.33.2 Oct 31, 2023

renovate bot force-pushed the renovate/core-js-3.x branch from d38b0ee to 02605bd Compare November 20, 2023 08:34

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.33.2~~ chore(deps): update dependency core-js to v3.33.3 Nov 20, 2023

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.33.3~~ chore(deps): update dependency core-js to v3.34.0 Dec 6, 2023

renovate bot force-pushed the renovate/core-js-3.x branch from 02605bd to 9e04ee3 Compare December 6, 2023 14:44

renovate bot force-pushed the renovate/core-js-3.x branch from 9e04ee3 to c5e219d Compare December 29, 2023 05:15

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.34.0~~ chore(deps): update dependency core-js to v3.35.0 Dec 29, 2023

renovate bot force-pushed the renovate/core-js-3.x branch from c5e219d to 47416b8 Compare January 21, 2024 08:46

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.35.0~~ chore(deps): update dependency core-js to v3.35.1 Jan 21, 2024

renovate bot force-pushed the renovate/core-js-3.x branch from 47416b8 to 87d3eb1 Compare February 15, 2024 02:06

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.35.1~~ chore(deps): update dependency core-js to v3.36.0 Feb 15, 2024

chore(deps): update dependency core-js to v3.36.1

1db6e03

renovate bot force-pushed the renovate/core-js-3.x branch from 87d3eb1 to 1db6e03 Compare March 19, 2024 20:40

renovate bot changed the title ~~chore(deps): update dependency core-js to v3.36.0~~ chore(deps): update dependency core-js to v3.36.1 Mar 19, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency core-js to v3.36.1 #7

chore(deps): update dependency core-js to v3.36.1 #7

renovate bot commented Oct 12, 2021 •

edited

Loading

chore(deps): update dependency core-js to v3.36.1 #7

Are you sure you want to change the base?

chore(deps): update dependency core-js to v3.36.1 #7

Conversation

renovate bot commented Oct 12, 2021 • edited Loading

Release Notes

Configuration

renovate bot commented Oct 12, 2021 •

edited

Loading