Implement unit tests for IDB provider

[fabioh8010]

Details

Proposal: https://expensify.slack.com/archives/C05LX9D6E07/p1765532047195689

This PR:

• Implements unit tests for the IDB provider (web) by using fake-indexeddb.
• Fixes the following issues in the IDB provider:
  • setItem removes and redundantly sets the value to null
  • multiSet calls multiple removeItem's instead of delMany
  • multiMerge calls multiple removeItem's instead of using the transaction
  • Index misalignment between pairs and values in multiMerge
  • Primitives are incorrectly stored when using multiMerge (widespread issue)

Related Issues

Expensify/App#71203

Automated Tests

Unit tests were created/updated to cover the fixes above.

Manual Tests

Basic test in E/App:

1. Login with a account.
2. Navigate to a chat, send a message. React to that message.
3. Reply to that message in a new thread.
4. Create a new task, navigate to its details and mark it as completed.
5. Create a new expense to someone else, navigate to its details.
6. Go to Reports tab, Expenses, assert you can find your expense and see its details.
7. Create a new workspace, assert the rooms were created, delete it afterwards.

Author Checklist

• I linked the correct issue in the ### Related Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Screen.Recording.2025-12-11.at.23.01.31-compressed.mov

Android: mWeb Chrome

Screen.Recording.2025-12-11.at.23.06.45-compressed.mov

iOS: Native

Screen.Recording.2025-12-11.at.23.13.24-compressed.mov

iOS: mWeb Safari

Screen.Recording.2025-12-11.at.23.16.46-compressed.mov

MacOS: Chrome / Safari

Screen.Recording.2025-12-11.at.23.19.44-compressed.mov

MacOS: Desktop

Screen.Recording.2025-12-11.at.23.21.32-compressed.mov

[fabioh8010]

cc @VickyStash

[shubham1206agra]

@VickyStash We have deprecated the App for Electron. So, do we still need this logic?

[VickyStash]

Considering starting this PR, all providers are initialized lazily (all providers got a new init method), so I think we would want to keep it this way even with deprecated electron.
@shubham1206agra What do you think?

[shubham1206agra]

@VickyStash It's fine

[Beamanator]

Make sense to me, though should we remove (e.g. electron main process)? Maybe a different example would be useful to mention?

[shubham1206agra]

@VickyStash Please use for ... of here instead of forEach.

[VickyStash]

Updated in 616d497

[shubham1206agra]

@VickyStash Add tests for Date and RegExp here as they are technically objects that should be replaced, not merged.

[VickyStash]

Updated in 5b0dd48

[VickyStash]

@shubham1206agra Thank you for the feedback, I'll get back to it later today tomorrow morning (I've spend more time then expected on another issue)!

[shubham1206agra]

@VickyStash Can you do for...of instead of forEach in every place you made the change?

[VickyStash]

Done in 14115ad

[VickyStash]

I'll be OOO Dec 20 - 28, and then Dec 31 - Jan 6 🎄
@kubabutkiewicz will keep an eye on the PR during this time

[shubham1206agra]

@Beamanator Bump here

[Beamanator]

Oops sorry team! Reviewing now! Mostly back from OOO 🙏

[Beamanator]

Overall looking really great here, I think we should move forward!

[os-botify]

🚀 Published to npm in 3.0.27 🎉