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

[dependabot[bot]]

Bumps core-js from 3.19.1 to 3.25.0.

Changelog

Sourced from core-js's changelog.

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

3.24.1 - 2022.07.30

• 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

3.24.0 - 2022.07.25

• 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

3.23.5 - 2022.07.18

• Fixed a typo in the structuredClone feature detection, #1106

... (truncated)

Commits

• b61f3c3 3.25.0
• 7750751 improve notes
• ea7645f add Object.prototype.__proto__ polyfill
• 9e70176 fix omitting the result of proxing .return in `%IteratorHelperPrototype%.re...
• 4910371 update dependencies
• 4c9c6d6 add missed NodeJS 13.2 to esmodules core-js-compat / core-js-builder ta...
• 9f4af1f fix a typo
• 0400dea some stylistic changes and minor fixes
• c76303d update dependencies
• 95fc85d fix ArrayBuffer.length in V8 ~ Chrome 27-
• 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	Aug 29, 2022 at 5:37AM (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.