Browser Extension
The popup
Click the Fuego DevTools button in the toolbar to see which Firebase project a page uses, its SDK version and products, the signed-in Auth user with custom claims and token expiry, utilities for JSON, timestamps, push IDs and ID tokens, and links to the project's pages in the Firebase and Google Cloud consoles.
Click the Fuego DevTools button in the toolbar. The popup has three tabs: This page (the page’s Firebase project, its signed-in user and the badge), Utilities and Links.
Firebase on this page
The popup reads the page you are on, at that moment, and its This page tab shows Firebase on this page:
- the project id, with its
authDomain, or with the emulators’ ports when the page talks to the Firebase emulators; - the SDK version;
- the products the page uses: Firestore, Auth, Realtime Database, Storage, Functions, Cloud Messaging, Analytics, Remote Config, App Check, Performance Monitoring, AI Logic;
- Open in Fuego or Add to Fuego for that project (see Opening things in Fuego);
- Copy config: the Firebase web config the page holds, as you would pass
it to
initializeApp, with only the fields the page shows.
Otherwise it says No Firebase on this page (the page has not loaded Firebase, or has not used it yet), The browser does not let extensions read this page (the browser’s own pages and the extension stores), or Project not visible yet.
The popup reads only what the page already holds: its Firebase configuration, the records the Firebase SDKs keep in the page’s storage, and which Firebase addresses the page has already called. It never makes a request, never writes to the page’s storage and never probes security rules.
Signed-in user
When the page holds a signed-in Firebase Auth user, the Signed-in user card shows:
- the name or email, the uid, the sign-in provider and when the ID token expires (“token expires in 42 min”, or “token expired”), plus the tenant and “emulator token” when they apply;
- Claims: the custom claims, decoded on this computer;
- Show token and Copy ID token: the ID token, read from the page only when you click;
- Open in Fuego: the user in Fuego’s Firebase Authentication view.
When the page holds more than one user, the card lists the others (“Other signed-in users: …”). The refresh token never leaves the page.
The popup reads the user the Firebase Auth SDK keeps in the page (in IndexedDB, local storage or session storage). For an app that keeps its user in memory only, the popup shows no Signed-in user card; the panel’s Auth tab then says No signed-in user stored on this page.
The panel’s Auth tab in DevTools shows the same users, with Read again, and the Auth calls of the Recording (time, call and result). Tokens are never recorded, and an export keeps Auth calls as events, without who signed in.
Utilities
The Utilities tab holds four tools that run on this computer and send nothing; click one to open it:
| Utility | What it does |
|---|---|
| Firestore REST JSON ↔ Fuego JSON | Paste a document from the Firestore REST API (typed values such as {"stringValue": "Mug"}) to get Fuego JSON, or Fuego JSON to get the REST form |
| Timestamp converter | Reads epoch seconds, milliseconds, microseconds or nanoseconds, ISO 8601 or {seconds, nanos}, and gives every other form: UTC, local time, Fuego JSON and the REST timestampValue |
| Push ID → creation date | When a Realtime Database push key (-NqT3k9aB2cD4eF6gH8i) was created |
| Decode an ID token | The uid, project, sign-in provider, email, issue and expiry times and custom claims of a Firebase ID token. It decodes, it does not check the signature; an Auth emulator token shows as unsigned |
Links
The Links tab opens the project’s pages in the Firebase console and in the Google Cloud console, each in a new tab:
| Console | Pages |
|---|---|
| Firebase console | Project overview, Firestore, Authentication, Storage, Realtime Database, Functions, Hosting, Remote Config, App Check, Project settings, Usage and billing |
| Google Cloud console | Dashboard, Firestore, Cloud Run functions, Cloud Run, Cloud Storage, Identity Platform, Logs Explorer, IAM, API credentials, Secret Manager, Billing |
Project starts with the page’s project; type another project ID to open its pages instead. For the page’s own project, Firestore, Storage and the Realtime Database open on the database, bucket and instance the page uses. Without a project, the Firebase console asks which one to open and the Google Cloud console opens the last one you used.
When the page talks to the Firebase emulators, the links
still open the project in the cloud, and Emulator Suite UI opens the
emulators’ own UI on port 4000, its default. A demo- project exists only in
the emulators, so Project starts empty.
The badge
Show a badge when a page uses Firebase (on the This page tab and in the settings) marks the toolbar button with a dot, in Fuego’s purple, on pages that use Firebase. It is off until you turn it on.
To see that, Fuego DevTools needs access to the sites you visit, so your browser asks for it when you turn the badge on. It uses that access only to look for Firebase, and nothing leaves your computer. Turning the badge off gives the access back. If you decline, the popup says “The browser did not grant access, so the badge stays off.”
The badge looks at what a site keeps in the browser, so a page of a site whose other pages used Firebase may get it too.
Settings
Settings at the top of the popup opens the extension’s settings:
- Toolbar badge: the switch above.
- Opening in Fuego: whether to show the window that explains how to get Fuego when Fuego cannot be reached (see Opening things in Fuego).
- Cost estimates: the database location, edition and gross cost for projects you have not set up in the DevTools panel (see Cost settings).
