flog check allEXPERIMENTAL
Experimental: This check may change before stabilization. It remains read-only and retains every workspace result in its report.
Run all workspace checks and retain every result in one report.
Usage#
flog check all --workspace <selector> [--json]
Examples#
flog check all --workspace apps/website
flog check all --workspace @example/library --json
--workspace must select exactly one workspace by name, path, owned file, or a
glob with one match. The command resolves that workspace once, then runs the
existing peers, types, imports, and dependency checks for the same package. It
does not execute checked source or start subprocesses.
The checks always run in peers, types, imports, deps order. A finding or
incomplete result from one check does not suppress later checks. Human output
gives a deterministic summary for each component. --json emits one versioned
report containing workspace identity, aggregate completeness and cleanliness,
and each check's coverage, findings or diagnostics, and uncertainty or error.
Peer-removal candidates remain advisory in this aggregate command, just as they
are for flog check peers without --fail-on-candidates. The aggregate command
does not offer that policy flag.
Exit status 0 means every check completed without a failing finding. Status 1 means all checks completed but types, imports, or dependency-use checks found an error. Status 5 takes precedence when any check is incomplete or fails operationally; all available component results are still emitted. Selection and option errors exit 2.
The component coverage boundaries do not expand in aggregate mode. Type checks remain per-file Stick checks, import checks remain bounded to supported static imports, dependency-use checks remain conservative, and peer checks retain their registry-backed graph semantics.