Progress

A progress run has four steps: start with a total, advance with the current position, optional notices, and finish with a verdict.

Rust

TerminalProgress is always available. It draws a live bar only when the optional progress feature (which adds indicatif) is enabled:

cargo add runemark --features progress

use runemark::{ColorMode, Console, ProgressMode, ProgressSink, TerminalProgress, Verdict};
use std::io::IsTerminal;

let progress = TerminalProgress::stderr(
    ProgressMode::Auto,
    Console::stderr(ColorMode::Auto),
    std::io::stderr().is_terminal(),
);
progress.start(10, "Auditing URLs");
progress.advance(1, "https://example.com");
progress.finish(Verdict::Passed, "Audit complete");

With the feature, ProgressMode::Auto shows a live bar in an interactive terminal and switches to a compact, line-oriented lifecycle when output is redirected, so stdout stays clean for machine-readable results. Without the feature, TerminalProgress always uses that lifecycle (or nothing, for ProgressMode::Never). PlainProgress and SilentProgress implement the same ProgressSink trait and need no feature either.

TerminalProgress::is_interactive reports which of the two a sink ended up being. That is not derivable from ProgressMode: Auto resolves against the stream the caller passed and against indicatif’s own view of the terminal, which hides its output where TERM is unset or dumb. A caller that prints its own lines during a run needs the answer — a live bar owns the last line of the terminal, and writing into it corrupts the frame.

The Node package has no equivalent; createProgress makes the same decision internally.

Node

const { createProgress } = require('@casoon/runemark')

const progress = createProgress({ mode: 'auto' })
progress.start(pages.length, 'Checking pages')
pages.forEach((page, index) => progress.advance(index + 1, page))
progress.finish('passed', 'Audit complete')

Progress writes to stderr. In auto mode the terminal check uses stderr unless isTerminal is set.