Update dependency fake-indexeddb to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
fake-indexeddb	^4.0.1 → ^6.0.0

---

Release Notes

dumbmatter/fakeIndexedDB (fake-indexeddb)

v6.2.5

Compare Source

• Add support for handleEvent and capture to improve Event compatibility (#​162 by @​nolanlawson)

• Improve handling some edge cases related transaction timing (#​165, #​168 by @​nolanlawson)

• More testing infrastructure improvements (#​164, #​166 by @​nolanlawson)

v6.2.4

Compare Source

• Several small bug fixes to more correctly handle various edge cases and increase the number of passing tests from the Web Platform Tests (#​147, #​155, #​157 by @​dumbmatter; #​156, #​158, #​159, #​160 by @​nolanlawson)

• Improvements to testing infrastructure, allowing more Web Platform Tests to run (#​148 by @​dumbmatter; #​150, #​151, #​152, #​153, #​154 by @​nolanlawson)

• Automated and updated the Web Platform Tests comparison table in the README (#​161 by @​nolanlawson)

v6.2.3

Compare Source

• Several small bug fixes to more correctly handle various edge cases and increase the number of passing tests from the Web Platform Tests (#​137, #​139, #​141, #​142, #​143, #​144, #​145, #​146 by @​nolanlawson)

v6.2.2

Compare Source

• Fixed regression in v6.2.0 where overwriting the global indexedDB variable created by fake-indexeddb/auto (such as with indexedDB = new IDBFactory();) was no longer working (#​135 by @​nolanlawson)

v6.2.1

Compare Source

• Fixed the IDBDatabase variable created by a CommonJS require of fake-indexeddb/auto, which was broken in v6.2.0 (#​131 by @​nolanlawson)

v6.2.0

Compare Source

• Fixed regression in v6.2.0 where overwriting the global indexedDB variable created by fake-indexeddb/auto (such as with indexedDB = new IDBFactory();) was no longer working (#​135 by @​nolanlawson)

v6.1.0

Compare Source

• Added support for new IndexedDB features: querying keys and values at the same time with getAllRecords, and passing a descending direction into getAll/getAllKeys. (#​112 by @​nolanlawson)

• Better DOMStringList polyfill that doesn't include various inappropriate array methods. (#​66 by @​dumbmatter)

• Updated the Web Platform Tests from 2019 to 2025 which improved test coverage and uncovered a few minor bugs that were fixed. (#​117 by @​nolanlawson)

v6.0.1

Compare Source

• #​110 - Fix handling of "undefined value" vs "missing value" in IDBObjectStore.add/put when that value is at the keyPath and autoIncrement is true - it should throw an error if the keyPath value is undefined, but previously it was not.

v6.0.0

Compare Source

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 - 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 - @​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 - @​sjnho fixed handling of Date objects to account for some edge cases, including jsdom overriding the native Date constructor.

v5.0.2

Compare Source

• #​94 - Improved performance of IDBObjectStore.count and IDBIndex.count.

v5.0.1

Compare Source

• #​89 - Fixed bug where ArrayBuffer views were not being correctly handled when used as keys.

• #​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

Compare Source

• Dropped support for Node.js 16, which allows me to get rid of the structuredClone polyfill, which reduces the package size by roughly 50%.

v4.0.2

Compare Source

• #​84 - Fix the TypeScript types in some situations.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: ts-jest@27.1.4
npm error Found: jest@30.2.0
npm error node_modules/jest
npm error   dev jest@"^30.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jest@"^27.0.0" from ts-jest@27.1.4
npm error node_modules/ts-jest
npm error   dev ts-jest@"^27.1.4" from the root project
npm error
npm error Conflicting peer dependency: jest@27.5.1
npm error node_modules/jest
npm error   peer jest@"^27.0.0" from ts-jest@27.1.4
npm error   node_modules/ts-jest
npm error     dev ts-jest@"^27.1.4" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-16T11_28_11_539Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-16T11_28_11_539Z-debug-0.log

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview