The line grammar
Every user-facing line is a prefix followed by one sentence, one concern per line:
All five channels occupy the same three glyph columns, so output stays aligned no matter what happened. The color carries the severity, not the glyph.
The debug channel only prints under
--debug or EXTENSION_DEBUG=1. Debug adds searchable key=value lines and never rewrites a line you would have seen anyway.
The identity card
At boot, a command prints one identity card per browser and dist pair:n/a placeholder, so row presence tells you what the session actually knows. There is no Binary row. build swaps the Profile and Run ID rows for an Output row.
From the release after 4.1.39, the Browser row says where the binary came from when you can act on it:
(pinned with --chromium-binary)names the flag or the variable that chose the binary, such as(pinned with FIREFOX_BINARY).(system install)marks a browser found on your system, for a target thatextension installcovers.- A managed binary gets no note.
- A Firefox nightly reads
Firefox Nightly, so nobody takes it for a release build.
binary in ready.json. See How the binary is chosen.
Lines under the card
From the release after 4.1.39, adev card carries extra lines when the session has something that the production build lacks:
Dev only line lists permissions, host access, or web accessible resources that only the dev manifest has. From the release after 4.2.0, a Dev only line that starts with manifest names the other manifest fields that the dev build changed and the production build does not have, such as externally_connectable.ids *. A Dev flag line names a launch flag that changes what you see, and the config key that flips it. The reasons live in ready.json under devAdditions.
A Dev pref line names a browser preference that the session wrote to a profile that outlives it:
One fact once
Every session fact has exactly one home:- Session identity (versions, browser, extension ID, profile, binary) lives in the card, only.
- Events (compiled, recompiling, exited) are flow lines.
- Diagnostics are debug
key=valuelines.
Warnings fire at the moment they apply
A warning prints immediately before the action it concerns, not at the end of the run. When you see a yellow line, the very next thing the CLI does is the thing the warning describes. That ordering means you never scroll back through a summary to find out which step a warning belonged to.Add-on or Extension
The artifact noun follows the engine. On Gecko targets (Firefox, Waterfox, LibreWolf) the CLI saysAdd-on. On Chromium and Safari targets it says Extension. Edge ships extensions through a store named Add-ons, but the artifact is still an Extension.
From the release after 4.1.39, the background follows the engine too. Where doctor and the act verbs say service worker on Chromium, they say background page on Firefox, because Firefox runs an extension’s background as a page.
Reading a colorless CI log
CI logs usually strip color, and meaning never lives only in color. In a colorless log:- Every
⏵⏵⏵line is info, success, warn, or error. Read the sentence, the copy states the outcome on its own. - Every
···line is debug output, safe to ignore unless you are diagnosing. - Errors follow a fixed anatomy: a label line, uppercase evidence rows such as
PATHorREASON, then an imperative remedy.
Module build failed (from ...) line and the stack trace are gone. Set EXTENSION_DEBUG=1 to see the stack.
From the release after 4.1.39, the bundler’s errors and warnings drop their color too, in build and in dev. They print as plain text when the output is not a terminal or NO_COLOR is set. FORCE_COLOR=1 keeps the color, and FORCE_COLOR=0 turns it off.
From the release after 4.1.41, a warning or an error line names its severity in words when color is off. Color is off when the output is not a terminal, or when NO_COLOR or FORCE_COLOR=0 is set. A warning line then reads ⏵⏵⏵ Warning:, and an error line reads ⏵⏵⏵ Error:. The compile summary keeps the bare glyph. Colored output and --output json do not change.
For machines, do not parse the human stream at all. Pass --output json for a single result envelope, and read session state from ready.json and events.ndjson under dist/extension-js/<browser>/.
Next steps
- Learn where the machine-readable session files live in Session artifacts.
- See the flags that shape output in Global flags.

