Output Formats
Use the --format flag to control how diagnostics are rendered.
default
Human-readable terminal output with colored code snippets and diagnostic highlighting.
In color-enabled terminals, start is cyan and bold, success is green, and error is red. The complete parenthesized execution details are rendered dim.
With --type-check, type errors are also included (see Type Checking for details):
Combined mode reports one canonical file count: the deduplicated union of lint targets and compiler roots. This remains accurate when CLI arguments and rslint ignore patterns restrict the lint phase while type-check follows each tsconfig's program-wide scope.
The machine-readable formats below emit diagnostics only on stdout. They do not include default-format lifecycle/status text, thread counts, or fix counts. With --timing, the timing table remains on stderr.
jsonline
One diagnostic per line as compact JSON. Suitable for programmatic consumption.
github
GitHub Actions workflow command format. Creates annotations directly on pull request diffs.
gitlab
GitLab Code Quality report format. A single JSON array, suitable for the codequality report artifact that GitLab CI uses to annotate merge requests.
Error diagnostics map to major severity and warnings map to minor. To wire this into a pipeline, add the report as a codequality artifact in .gitlab-ci.yml: