Update core-js: 3.24.1 → 3.25.5 (minor)

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ core-js (3.24.1 → 3.25.5) · Repo · Changelog

Release Notes

3.25.5

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

3.25.4

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

3.25.3

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

3.25.2

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

3.25.1

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 duplications 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

3.25.0

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

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Travis-CI](https://travis-ci.com) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@depfu rebase
Rebases against your default branch and redoes this update

@depfu recreate
Recreates this PR, overwriting any edits that you've made to it

@depfu merge
Merges this PR once your tests are passing and conflicts are resolved

@depfu close
Closes this PR and deletes the branch

@depfu reopen
Restores the branch and reopens this PR (if it's closed)

@depfu pause
Ignores all future updates for this dependency and closes this PR

@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR

@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

idahogurl / vs-code-prettier-eslint