chore(deps): update dependency fake-indexeddb to v6

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
fake-indexeddb	^4.0.2 -> ^6.0.0

---

Release Notes

dumbmatter/fakeIndexedDB (fake-indexeddb)

### [`v6.0.0`](https://togithub.com/dumbmatter/fakeIndexedDB/blob/HEAD/CHANGELOG.md#600-2024-05-20) [Compare Source](https://togithub.com/dumbmatter/fakeIndexedDB/compare/v5.0.2...v6.0.0) I made this a new major version because it includes a few changes that could in theory break something in some weird situations. But I think the vast majority of users (possibly all users?) won't have any issue upgrading. - [#​48](https://togithub.com/dumbmatter/fakeIndexedDB/issues/48) - Switched to using `DOMException` errors rather than normal errors, since that's what the IndexedDB spec says to use, and Node.js now has a built-in DOMException in all supported versions. - [#​93](https://togithub.com/dumbmatter/fakeIndexedDB/issues/93) - [@​bryan-codaio](https://togithub.com/bryan-codaio) made the latest tweak to event scheduling, this time improving how `setImmediate` is used in some situations where people are mocking timers. - [#​99](https://togithub.com/dumbmatter/fakeIndexedDB/issues/99) - [@​sjnho](https://togithub.com/sjnho) fixed handling of `Date` objects to account for some edge cases, including jsdom overriding the native `Date` constructor. ### [`v5.0.2`](https://togithub.com/dumbmatter/fakeIndexedDB/blob/HEAD/CHANGELOG.md#502-2023-12-30) [Compare Source](https://togithub.com/dumbmatter/fakeIndexedDB/compare/v5.0.1...v5.0.2) - [#​94](https://togithub.com/dumbmatter/fakeIndexedDB/issues/94) - Improved performance of `IDBObjectStore.count` and `IDBIndex.count`. ### [`v5.0.1`](https://togithub.com/dumbmatter/fakeIndexedDB/blob/HEAD/CHANGELOG.md#501-2023-10-25) [Compare Source](https://togithub.com/dumbmatter/fakeIndexedDB/compare/v5.0.0...v5.0.1) - [#​89](https://togithub.com/dumbmatter/fakeIndexedDB/issues/89) - Fixed bug where ArrayBuffer views were not being correctly handled when used as keys. - [#​88](https://togithub.com/dumbmatter/fakeIndexedDB/issues/88) - Added explanation to README.md about how to use fake-indexeddb v5+ with jsdom, since a `structuredClone` polyfill is not included anymore. ### [`v5.0.0`](https://togithub.com/dumbmatter/fakeIndexedDB/blob/HEAD/CHANGELOG.md#500-2023-10-13) [Compare Source](https://togithub.com/dumbmatter/fakeIndexedDB/compare/v4.0.2...v5.0.0) - Dropped support for Node.js 16, which allows me to get rid of the `structuredClone` polyfill, which reduces the package size by roughly 50%.

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/Toronto, 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.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 83.69%. Comparing base (1a6ff30) to head (1a6ff30).

:exclamation: Current head 1a6ff30 differs from pull request most recent head d1d65a1

Please upload reports for the commit d1d65a1 to get more accurate results.

Additional details and impacted files

[](https://app.codecov.io/gh/alixlahuec/zotero-roam/pull/644?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Alix+Lahuec) ```diff @@ Coverage Diff @@ ## beta #644 +/- ## ======================================= Coverage 83.69% 83.69% ======================================= Files 158 158 Lines 4917 4917 Branches 1409 1409 ======================================= Hits 4115 4115 Misses 777 777 Partials 25 25 ```

[renovate[bot]]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.