Problem
Node installation can produce hundreds of lines of per-package progress output from the underlying cm-cli / pip subprocesses. This becomes difficult to review when installing many node packs, especially when terminal progress bars are captured as separate log lines.
This was previously discussed in #442. The maintainer suggested opening a focused request for a --quiet-style flag.
Proposed behavior
Add a --quiet flag to the applicable node installation commands.
When --quiet is enabled:
- Suppress routine subprocess progress bars and per-package download progress.
- Keep warnings and errors visible.
- Show a concise final success/failure result for each requested node pack.
- Preserve the normal exit code so scripts can reliably detect failures.
Without --quiet, keep the current output unchanged for backward compatibility.
Expected result
Installing many node packs with --quiet should produce a short, reviewable log containing the requested node packs, important warnings/errors, and final results, without a separate line for every progress-bar update.
Problem
Node installation can produce hundreds of lines of per-package progress output from the underlying
cm-cli/pipsubprocesses. This becomes difficult to review when installing many node packs, especially when terminal progress bars are captured as separate log lines.This was previously discussed in #442. The maintainer suggested opening a focused request for a
--quiet-style flag.Proposed behavior
Add a
--quietflag to the applicable node installation commands.When
--quietis enabled:Without
--quiet, keep the current output unchanged for backward compatibility.Expected result
Installing many node packs with
--quietshould produce a short, reviewable log containing the requested node packs, important warnings/errors, and final results, without a separate line for every progress-bar update.