[codad5]

What

The packager can print a command's output while it runs.

Build::plugin(__DIR__)
    ->verbose()                       // every command: run(), composer(), scope(), make-pot
    ->run('npm ci', 'npm run build')
    ->zip();

Build::plugin(__DIR__)
    ->run('npm ci')                   // quiet
    ->runVerbose('npm run build')     // streamed
    ->zip();

Also wptoolkit-build package --verbose and "verbose": true in wptoolkit.json.

Why

Output was captured and shown only when a command failed, so a slow asset build looked hung and CI logs said nothing about what ran.

Behaviour

• Default is unchanged: quiet.
• Streamed line by line through the build's output channel, indented under the command ( | line). stderr is included.
• Output is still captured and returned.
• A failing command that was streamed repeats only its last 20 lines in the error (the rest was already printed); a quiet one still shows everything.
• New StreamingCommandRunner interface extends CommandRunner, so existing runner implementations keep working; with one of those, verbose output is printed when the command ends.
• A build-wide switch rather than an argument on run(), because run() is variadic and composer()/scope() run long commands too.

Tests

Written first, six of eight seen failing. They run real child processes: default quiet, verbose (stdout and stderr, ordering), runVerbose for one command, line-by-line callback, failure tail when streamed, full output when quiet, non-streaming runner fallback, config file. Liveness checked by hand: a line arrives two seconds before the next one the command prints.

🤖 Generated with Claude Code