chore(deps-dev): bump fake-indexeddb from 3.1.3 to 4.0.2

[dependabot]

Bumps fake-indexeddb from 3.1.3 to 4.0.2.

Release notes

Sourced from fake-indexeddb's releases.

v4.0.2

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

v4.0.1

• #79 - Added missing request accessor to the FDBCursor object. Thank you @​mmacfadden for the PR!

v4.0.0

TLDR: Most users can upgrade without doing any extra work, but you might need to change require("fake-indexeddb") to require("fake-indexeddb").default. All other ways of importing fake-indexeddb (such as with import, or requiring sub-modules like require("fake-indexeddb/auto") or require("fake-indexeddb/lib/FDBKeyRange")) should continue working like normal.

Details:

• #23 - TypeScript support! As of version 4, fake-indexeddb includes TypeScript types. As you can see in types.d.ts, it's just using TypeScript's built-in IndexedDB types, rather than generating types from the fake-indexeddb code base. The reason I did this is for compatibility with your application code that may already be using TypeScript's IndexedDB types, so if I used something different for fake-indexeddb, it could lead to spurious type errors. In theory this could lead to other errors if there are differences between Typescript's IndexedDB types and fake-indexeddb's API, but currently I'm not aware of any difference.

• Added support for ES modules in addition to CommonJS modules. That means you can import or require and it should just work.

• Breaking change: The easiest way to use this module is still to import/require "fake-indexeddb/auto". If instead you want to import an individual variable rather than populate the global scope with all of them, previously you would do const indexedDB = require("fake-indexeddb"); for the main indexedDB variable and const IDBKeyRange = require("fake-indexeddb/lib/FDBKeyRange"); for any of the other IndexedDB variables. In this release, I made everything a named export of the main package, so you can do:

  import { indexedDB, IDBKeyRange } from "fake-indexeddb";

  or

  const { indexedDB, IDBKeyRange } = require("fake-indexeddb");

  For backwards compatibility, the require("fake-indexeddb/lib/FDBKeyRange") syntax still is supported, but the new exports of the main module are a breaking change. indexedDB is still the default export, but in CommonJS you can't have both default and named exports, so the default export is really just an property named "default". This may requrie changing requires of the root module like require("fake-indexeddb") to require("fake-indexeddb").default. Or switch to ES modules and import it :)

• Breaking change: Dropped support for versions of Node.js older than Node 12.

• Breaking change: For environments with a built-in structuredClone function (such as Node.js 17+), that is used rather than the realistic-structured-clone NPM module. There are some differences between the two implementations of the structured cloning algorithm, but probably nothing noticable, and probably all is in the direction of better spec compliance such as this or this. There is also a minor performance increase with the built-in function - the test suite of fake-indexeddb runs about 5% faster.

v3.1.8

• #74 - Fixed error when adding undefined or null children in indexed objects, by @​lukebrody

v3.1.7

• #71 - Fixed an error when used with jest/jsdom introduced in version 3.1.6.

v3.1.6

• #70 - Fixed performance regression in the previous version. Thank you @​joshkel for figuring this out!

v3.1.4

• #67 - Fixed compatibility with jsdom by replacing all uses of setImmedaite with setTimeout.

Changelog

Sourced from fake-indexeddb's changelog.

4.0.2 (2023-07-14)

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

4.0.1 (2022-11-29)

• #79 - Added missing request accessor to the FDBCursor object. Thank you @​mmacfadden for the PR!

4.0.0 (2022-07-02)

TLDR: Most users can upgrade without doing any extra work, but you might need to change require("fake-indexeddb") to require("fake-indexeddb").default. All other ways of importing fake-indexeddb (such as with import, or requiring sub-modules like require("fake-indexeddb/auto") or require("fake-indexeddb/lib/FDBKeyRange")) should continue working like normal.

Details:

• #23 - TypeScript support! As of version 4, fake-indexeddb includes TypeScript types. As you can see in types.d.ts, it's just using TypeScript's built-in IndexedDB types, rather than generating types from the fake-indexeddb code base. The reason I did this is for compatibility with your application code that may already be using TypeScript's IndexedDB types, so if I used something different for fake-indexeddb, it could lead to spurious type errors. In theory this could lead to other errors if there are differences between Typescript's IndexedDB types and fake-indexeddb's API, but currently I'm not aware of any difference.

• Added support for ES modules in addition to CommonJS modules. That means you can import or require and it should just work.

• Breaking change: The easiest way to use this module is still to import/require "fake-indexeddb/auto". If instead you want to import an individual variable rather than populate the global scope with all of them, previously you would do const indexedDB = require("fake-indexeddb"); for the main indexedDB variable and const IDBKeyRange = require("fake-indexeddb/lib/FDBKeyRange"); for any of the other IndexedDB variables. In this release, I made everything a named export of the main package, so you can do:

  import { indexedDB, IDBKeyRange } from "fake-indexeddb";

  or

  const { indexedDB, IDBKeyRange } = require("fake-indexeddb");

  For backwards compatibility, the require("fake-indexeddb/lib/FDBKeyRange") syntax still is supported, but the new exports of the main module are a breaking change. indexedDB is still the default export, but in CommonJS you can't have both default and named exports, so the default export is really just an property named "default". This may requrie changing requires of the root module like require("fake-indexeddb") to require("fake-indexeddb").default. Or switch to ES modules and import it :)

• Breaking change: Dropped support for versions of Node.js older than Node 12.

• Breaking change: For environments with a built-in structuredClone function (such as Node.js 17+), that is used rather than the realistic-structured-clone NPM module. There are some differences between the two implementations of the structured cloning algorithm, but probably nothing noticable, and probably all is in the direction of better spec compliance such as this or this. There is also a minor performance increase with the built-in function - the test suite of fake-indexeddb runs about 5% faster.

3.1.8 (2022-06-08)

• #74 - Fixed error when adding undefined or null children in indexed objects, by @​lukebrody

3.1.7 (2021-10-19)

• #71 - Fixed an error when used with jest/jsdom introduced in version 3.1.6.

3.1.6 (2021-10-19)

• #70 - Fixed performance regression in the previous version. Thank you @​joshkel for figuring this out!

3.1.4 (2021-10-11)

... (truncated)

Commits

• 92256e5 4.0.2
• 372c7fe Changelog
• b63520c More explicit types
• 6963357 Remove obsolete entry
• 7b5e263 Merge pull request #80 from homura/patch-1
• 42353b1 Update README.md
• 8deda8a docs: Import auto first to work with Dexie
• a92a72d 4.0.1
• d4583bc Changelog
• 4eb61f2 Merge pull request #79 from mmacfadden/master
• Additional commits viewable in compare view

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)

[dependabot]

Dependabot tried to add @iamnewton and @brodrigu as reviewers to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/MagniteEngineering/fledge.polyfill/pulls/375/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the MagniteEngineering/fledge.polyfill repository. // See: https://docs.github.com/rest/pulls/review-requests#request-reviewers-for-a-pull-request

[codecov-commenter]

Codecov Report

Patch and project coverage have no change.

Comparison is base (36ae8f5) 50.26% compared to head (633c20f) 50.26%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #375   +/-   ##
=======================================
  Coverage   50.26%   50.26%           
=======================================
  Files           8        8           
  Lines         189      189           
  Branches       34       34           
=======================================
  Hits           95       95           
  Misses         75       75           
  Partials       19       19           

Flag	Coverage Δ
unittests	50.26% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.