fix(deps): bump core-js from 3.31.1 to ^3.32.2 (main) #8877
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.31.1
->^3.32.2
Release Notes
zloirock/core-js (core-js)
v3.32.2
Compare Source
structuredClone
feature detection[email protected]
bug, #1288eval
bug, #1287v3.32.1
Compare Source
process
polyfill tocore-js
via some bundlers oresm.sh
, #1277Promise.withResolvers
marked as supported from Bun 0.7.1v3.32.0
Compare Source
Array
grouping proposal, July 2023 TC39 meeting updates:/actual/
namespaces entries, unconditional forced replacement changed to feature detectionPromise.withResolvers
proposal, July 2023 TC39 meeting updates:/actual/
namespaces entries, unconditional forced replacement changed to feature detectionSet
methods stage 3 proposal, July 2023 TC39 meeting updates:Set
sizes, proposal-set-methods/88IsCallable
check inGetKeysIterator
, proposal-set-methods/101String
wrapper objects, July 2023 TC39 meeting update, proposal-iterator-helpers/281Iterator
is not constructible from the active function object (works as an abstract class)/actual/
namespace entries, unconditional forced replacement changed to feature detection[@@​dispose]()
method when hint isasync-dispose
, proposal-explicit-resource-management/180Float16Array
stage 3 proposal:Float16Array
right now, however, make sense to add some methods from this proposal.Math.f16round
DataView.prototype.getFloat16
DataView.prototype.setFloat16
DataView
get / setUint8Clamped
methods stage 1 proposal:DataView.prototype.getUint8Clamped
DataView.prototype.setUint8Clamped
value
argument ofURLSearchParams.prototype.{ has, delete }
Set
methods implementation by the actual specSymbol.{ dispose, asyncDispose }
descriptors from NodeJS 20.4 / transpilers helpers / userland codeAsyncIteratorPrototype
core-js/configurator
option, #1268Iterator
helpers proposal features marked as supported from V8 ~ Chrome 117Array
grouping proposal features marked as supported from V8 ~ Chrome 117Symbol.{ dispose, asyncDispose }
as supported from NodeJS 20.5.0 (as mentioned above, NodeJS 20.4.0 add it, but with incorrect descriptors)Configuration
📅 Schedule: Branch creation - "before 5am on wednesday" in timezone Europe/Vienna, 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.
This PR has been generated by Mend Renovate. View repository job log here.