Browser Extension
Since v2.3.0Opening things in Fuego
With Fuego 2.3.0 or later on the same computer, Fuego DevTools opens what you are looking at in Fuego: from the popup, the DevTools panel, the Firebase console, Firestore Studio or a selected path. It starts Fuego when it is not running and offers to add a project Fuego does not have yet.
What it needs
- Fuego 2.3.0 or later on the same computer, on macOS, Windows or Linux. Fuego is a free download.
- To see the data, the project in Fuego, connected with an account that can read it (Adding a Firebase project). Add to Fuego helps with that.
Everything else in Fuego DevTools works without Fuego.
Where to open from
| Where | What opens |
|---|---|
| The popup, Firebase on this page | The page’s project; on a page that uses only the Realtime Database, its database (see The Realtime Database) |
| The popup, Signed-in user | The user, in Fuego’s Authentication view |
| The DevTools panel, an operation’s detail | Its query, document, collection or Storage file, or the node of a Realtime Database call |
| The DevTools panel, Auth tab | The user |
| The Firebase console and Firestore Studio | The collection, document or query on screen, and Exact JSON in Fuego |
| The Firebase console’s Authentication page | A user, or the project’s users (Open users in Fuego) |
| The Firebase console’s Realtime Database page | The node on screen, or a node of the tree |
| The right-click menu on selected text | A path, a resource name or a console link (see below) |
The panel has nothing to open for Auth calls. What opens, opens in the Fuego window you used last.
The first time
The first time you click Open in Fuego, a small window, Open this in Fuego, explains: “Fuego is a free desktop app for Firebase: it opens documents, collections and queries from here in one click.” It shows what would open (a document, a collection, a query, an Auth user, a Storage file, a Realtime Database location or a project), with its project, database and path, and offers:
- I have Fuego: your browser asks to let Fuego DevTools talk to apps on this computer (the exact words are in Permissions). Allow it, and what you clicked opens in Fuego.
- Get Fuego (free): the download page.
- Don’t show this again: from then on, when Fuego cannot be reached, Open in Fuego goes straight to your browser as a Fuego link, which the browser asks about each time and which opens Fuego if you have it (on Firefox, a Fuego it is allowed to look for and does not find gets no link: the button says Fuego not found). Turn the window back on in the extension’s settings, under Opening in Fuego.
The popup’s footer offers I have Fuego too, with the line “Fuego DevTools can open things in Fuego once you allow it.”
If you decline the browser’s request, or Fuego is not there, what you clicked goes to the browser as a Fuego link, and the window says Nothing happened? Update or get Fuego. On Firefox, once you have allowed it, a Fuego it does not find gets no link: the window says Fuego not found instead.
Once Fuego DevTools may talk to Fuego, a click that finds no Fuego opens the window as Fuego not found: “Fuego DevTools did not find Fuego on this computer. If you just installed it, open Fuego once, then try again.” with Get Fuego (free) and Try again. Fuego tells the browsers where to find it every time it starts, so a Fuego installed a moment ago has to be opened once.
Fuego’s status
The popup’s footer says what Fuego DevTools knows about Fuego:
| Status | Button |
|---|---|
| Fuego 2.3.0 is running · Acme Shop: its version and the project it has open | — |
| Fuego is not running | Launch Fuego |
| Fuego not found | Get Fuego (free) |
| Fuego DevTools can open things in Fuego once you allow it. | I have Fuego, Get Fuego (free) |
| This Fuego needs an update | Update Fuego: the download page |
| Fuego DevTools needs an update to work with this Fuego. | None: your browser updates extensions on its own, or from its extensions page |
Open in Fuego or Add to Fuego
Once Fuego DevTools may talk to Fuego, every button asks Fuego what it can open before you click, and reads:
- Open in Fuego: Fuego has the project. When Fuego is not running, the click starts it, then opens what you clicked there (“Fuego is starting…”). Fuego says which projects it has only while it runs: when it is not running the button reads Open in Fuego, and if Fuego does not have the project it opens its add-project dialog first.
- Add to Fuego: Fuego is running and does not have this project. Fuego opens its add-project dialog with the project id filled in; connect the project with an account that can read it, and what you clicked opens. Cancel, and nothing opens.
- Update Fuego to open this: your Fuego is too old for this; update it from the download page.
- Open in Fuego (not for emulators), disabled: emulator data never opens in Fuego from the browser. Fuego connects to the emulators on its own, on the plans that include them.
- Open in Fuego, disabled, with “Update Fuego DevTools to open this in this Fuego”: Fuego is newer than the extension, which your browser updates.
After a click the button says how it went: “Opened in Fuego”, “Fuego is starting…”, or what went wrong and what to do. When the link had to go through the browser, it says Nothing happened? Update or get Fuego: Fuego is missing, older than 2.3.0, or the browser’s question was dismissed.
On the Free plan
Fuego’s Free plan holds one project and does not include the emulators. If Fuego already has a project, Add to Fuego cannot add another one. If it has none, the project you add takes the plan’s one place: add the project you work on, not one you only want to look at, such as the demo’s, which your account cannot read anyway. Paid licenses have no project limit, unless your team sets one for your license.
The Realtime Database
A Realtime Database location opens on Fuego’s Realtime Database page, from:
- the DevTools panel: a Realtime Database call’s detail opens the node the call read, wrote or listened to. Its query stays in the panel’s Query tab: Fuego opens the node, not the query;
- the popup: on a page that uses the Realtime Database and no Firestore database, Firebase on this page opens the root of the page’s database instead of the project;
- the Firebase console’s Realtime Database page: the node on screen, or a node of the tree (see Console extras).
The right-click menu does not open Realtime Database locations: a selected link to the console’s Realtime Database page is not something it reads. Open the node from that console page instead.
These buttons need a Fuego that opens Realtime Database locations, and Fuego DevTools allowed to talk to it (The first time). Until then the panel and the console show no button for the Realtime Database (never Update Fuego to open this or Get Fuego) and the popup opens the page’s project as before. In Safari this holds for a Fuego in the Applications folder: Safari lets Fuego DevTools read nothing of a Fuego elsewhere, so there the buttons show with any Fuego and an older one says it cannot open the link. On a page that talks to the emulators, the panel shows the button in any case, disabled, as Open in Fuego (not for emulators). Fuego’s license must include the Realtime Database too: when it does not, a click says “The Realtime Database is turned off by your Fuego license.”
A Realtime Database call names its database, not its project. Fuego DevTools looks for the project in:
- Fuego, while it runs: the databases of the projects saved in Fuego, including those Fuego found the last time it listed a project’s databases (it remembers them on this computer). Not in Safari, where Fuego DevTools does not ask Fuego;
- the page’s Firebase config, whose
databaseURLnames the database: the popup and the panel read it from the page the way the popup reads the project, and only read it. In Safari the panel does not read it; - the database’s name: a default database is named after its project,
such as
my-project-default-rtdbformy-project; some older projects’ default database is namedmy-projectitself, which counts when Fuego or the Recording knows a project of that name.
In the panel, when none of them names the project, or two name different ones, Open in Fuego stays disabled and says why: open that project’s Realtime Database in Fuego once, then try again. In Safari that does not help, since Fuego DevTools learns nothing from Fuego there: open the database from its project in Fuego instead. A project Fuego does not have reads Add to Fuego, as for Firestore.
Right-click a path
Select text on any page, right-click and choose Open “…” in Fuego (the menu item shows what you selected). Fuego DevTools reads the selection as:
- a Firestore path, such as
users/alice: it opens in the project you have open in Fuego; with no project open, Fuego asks which one to use; - a resource name, such as
projects/my-project/databases/(default)/documents/users/alice: it opens in its own project and database; - a Firebase console or Firestore Studio link: it opens what the console shows, a query as a query (not a link to the console’s Realtime Database page).
Anything else is not a path. Firefox hides the item for it on the pages Fuego DevTools has access to: the Firebase console and the Google Cloud console, a tab where you clicked its toolbar button, and every site while the badge is on. Elsewhere, and always on Chrome and Edge, the item shows, and the window says Nothing to open in Fuego, with examples of what Fuego opens.
In Fuego
Fuego DevTools reaches Fuego through a small entry Fuego writes for the browsers on this computer (a “native messaging host”), at once when you turn the setting on and again every time Fuego starts:
- Settings ▸ Language and formats ▸ Browser extension: “Let the Fuego extension open things in Fuego”, on by default. Turned off, Fuego removes the entries it wrote and the extension finds no Fuego: it says Fuego not found, and sends Fuego links, which your browser asks about each time, only after Try again or with that window turned off (never on Firefox). On Linux, the entries for Firefox, Chrome, Chromium, Edge and Brave that Fuego’s DEB, RPM and Arch packages install for everyone on the computer stay until the package is removed, but while the setting is off the extension cannot reach Fuego through them either.
- Safari is the exception. Fuego DevTools for Safari opens Fuego through
its own app from the Mac App Store, not through these entries, so the
setting does not stop it there, and neither does
fuego extension uninstall. To stop it, turn Fuego DevTools off in Safari ▸ Settings ▸ Extensions. - From a terminal,
fuego extension statusshows each browser’s entry and when the extension last talked to Fuego,fuego extension installwrites them now andfuego extension uninstallremoves them: see Command line.
What Fuego opens are Fuego links: a document, collection, query, Storage file, Auth user, Realtime Database location or project, with the same rules as a link pasted anywhere else, such as the add-project dialog for a project Fuego does not have.
Related
- Windows, links and notifications: Fuego links
- Command line:
fuego extensionandfuego open - Adding a Firebase project
- Permissions, privacy and troubleshooting
