chore(deps-dev): bump core-js from 3.19.1 to 3.25.5

[dependabot[bot]]

Bumps core-js from 3.19.1 to 3.25.5.

Changelog

Sourced from core-js's changelog.

3.25.5 - 2022.10.04

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

3.25.4 - 2022.10.03

• 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 - 2022.09.26

• 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 - 2022.09.19

• 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 - 2022.09.08

• 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

3.25.0 - 2022.08.25

• 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

... (truncated)

Commits

• 4a8b1f7 3.25.5
• 1ad3e1a fix regression with an error on reuse of some built-in methods from another r...
• d59e440 3.25.4
• d76041c update lists of [Serializable] and [Transferable] objects in the `structu...
• fd7812a some stylistic changes, improve a note
• afcc148 update dependencies
• 14364db add Electron 22 compat data mapping
• 3172ef6 Merge pull request #1131 from AprilArcus/april/1130
• 8bd8508 Fix more Nashorn problems
• 44fe613 fix no-unused-vars setting
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by zloirock, a new releaser for core-js since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-checklist[bot]]

Example Check Group #2 (Click here to edit)

• [ ] Modify this checklist and click on the save button for it to appear on Github Pull Requests for this repo
• [ ] If you would like the checklist state to roll up to the Pull Request status, select the Enforce on Merge checkbox

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
dgiot-dashboard	✅ Ready (Inspect)	Visit Preview	Oct 4, 2022 at 5:26AM (UTC)

[pull-request-quantifier-deprecated[bot]]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .json : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.