chore: delete old config setup for compare scripts and get types from root node_modules/

[russellwheatley]

Description

• Resolve Firebase JS SDK comparison types from the installed root firebase package instead of checked-in copied snapshots.
• Flatten compare-types package configs into configs/.ts and update docs/imports accordingly.
• Add missing documented differences surfaced by comparing against live SDK declarations.
• Add a final per-package summary table to the compare-types output.

Now produces a nice summary at the end for ease of reference:

Related issues

Release Summary

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

---

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

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the type comparison infrastructure to eliminate the need for manual firebase-js-sdk type snapshots. By dynamically resolving types from the installed node_modules/firebase package, the process becomes more robust and easier to maintain. Additionally, the configuration files have been centralized into a dedicated directory, improving project structure and simplifying the registration of new packages.

Highlights

• Dynamic Type Resolution: Removed manual firebase-js-sdk type snapshots in favor of dynamically resolving types from the installed node_modules/firebase package.
• Centralized Configuration: Migrated all package-specific configuration files from individual package directories to a centralized configs/ directory.
• Enhanced Reporting: Added a new package summary table to the CLI output to provide a clearer overview of type comparison results.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the type comparison tool to dynamically resolve Firebase JS SDK types from the root node_modules instead of relying on manual snapshots, and moves package configurations to a dedicated configs/ directory. The reporting output is enhanced with a new package summary table. Feedback suggests adding a truthiness check for parsed JSON entries in the registry to prevent potential runtime crashes and improving terminal messages by replacing generic "" placeholders with actual package names for better clarity.

[mikehardy]

Really nice evolution for this tool - not surprised to see the AI and Pipelines divergence as I knew the upstream API expanded but the scope of the Pipelines expansion is still ... impressive. Moving quickly upstream there