`errors-only` output mode should communicate that only errors will be shown so it doesn't look like `turborepo` is hanging

[maschwenk]

Which project is this feature idea for?

Turborepo

Describe the feature you'd like to request

After enabling errors-only a bunch of folks on our team got confused because they thought Turborepo was hanging doing nothing.

Describe the solution you'd like

A really simple progress bar or just a banner letting folks know that's what's going on. This is a pretty silly feature request I'm aware but I think other folks will also ask the same question.

Describe alternatives you've considered

😆 explaining to 100+ developers who have been using turbo for ~2 years why turbo looks like its doing nothing

[maschwenk]

This is a change I’d happily have a stab at myself if people think it’s a good idea.

[arlyon]

I like this idea! Something like the following would be cool to show the current status.

$ turbo build --output-logs=errors-only
Packages in scope: my-app, my-lib
Running build in 2 packages

my-lib#build started
my-lib#build success
my-app#build started
my-app#build failed

# build output here
 
Tasks:    1 successful, 2 total
Cached:    0 cached, 2 total

Feel free to take a stab at this now if you'd like, or we can fold it in to a later release.

[maschwenk]

@arlyon one other thing I noticed is that errors-only seems to still print these:

Skipping cache check for @blah/blah, outputs have not changed since previous run.

At least in 1.7.4

[wycats]

@arlyon one other thing I noticed is that errors-only seems to still print these:

Skipping cache check for @blah/blah, outputs have not changed since previous run.

At least in 1.7.4

Still true in 1.9.1. It would be great to be able to turn these off.

[steveluscher]

Yes! Honestly I'd be happy with any of these

• errors-only gives you a little progress indicator, like @maschwenk suggested
• errors-only is actually hash-only but spits out errors if they happen
• hash-only spits out errors if it encounters one

cc/ @anthonyshew who's doing awesome work re: the CLI

[anthonyshew]

The UI released in 2.0 has some overlap here. Do the folks communicating on this issue think that it covers the concerns here?

This same behavior still exists when using streamed logs still, but interested to see if there's satisfaction from you all on this with the new TUI.