Progress update

[LarsKumbier]

I am using concurrently in a project with some long-running tasks.

It would be nice to have a progress bar as the last line, which indicates the jobs that are running at the moment, which have exited properly, and which have exited with a non-zero exit code.

I propose to activate it with the argument --progress

$ npm run test:all
> concurrently --progress npm:test:unit npm:test:integration npm:test:e2e
[test:unit] Started UnitTests
[test:integration] Started IntegrationTests
[test:e2e] Started e2eTests
[test:unit] npm run test:unit exited with code 0
[test:integration] Integration Tests failed! See reports/integration-tests.xml
[test:integration] npm run test:integration exited with code 1
[✔ test:unit] [❌ test:integration] [⌛ test:e2e]

The bottom line would change and be always visible, log output would append above it (similar to e.g. webpacks behavior).

Thoughts on the idea?

[gustavohenke]

I like this idea!
Would be open to receive PRs if anyone's brave to do it 🙂

[gustavohenke]

I'm looking into this (rough idea in branch https://github.com/open-cli-tools/concurrently/tree/issue-188).
Thinking about combining it with the --timings flag, to get the following combinations:

Detail level	Stickiness
Status only	❌ only when commands close
Status only	✅ updates live while commands run
Full table	❌ only when commands close (current --timings behaviour)
Full table	✅ updates live while commands run