test: tighten rules-unit-testing patch, matches upstream PR attempt

[mikehardy]

Description

Doing some dependency upgrades and I always look to trim the count of patches we carry, attempting to upstream this one now and the PR I proposed (after testing it...) is more minimal than our current in-tree patch, synching it here

works in testing, is minimal compared to previous

Related issues

See:

• fix: no pathname setter in some contexts, set during construction firebase/firebase-js-sdk#8861

Release Summary

Test-only code, no release

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
  • Other (macOS, web)
• My change includes tests;
  • e2e tests added or updated in packages/\*\*/e2e
  • jest tests added or updated in packages/\*\*/__tests__
• I have updated TypeScript types that are affected by my change.
• This is a breaking change;
  • Yes
  • No

Test Plan

Most of the database e2e tests uses the database/e2e/helpers.js::seed function, which uses this rules-unit-testing feature requiring the patch, if database e2e passes this works - and it passes for me locally

---

Think react-native-firebase is great? Please consider supporting the project with any of the below:

• 👉 Star this repo on GitHub ⭐️
• 👉 Follow React Native Firebase and Invertase on Twitter

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-firebase	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 24, 2025 2:54pm