Maybe provide some fallback if not on a TTY

[andywer]

Hey!

For https://github.com/andywer/npm-launch I was thinking about a plain-text fallback in case !require('tty').isatty(process.stdout). Right now you get all those control characters in the output when piping to a file or similar. In my particular case I have Jenkins/Travis builds in mind.

But maybe you are interested to solve that edge case directly in Listr?

[jokeyrhyme]

Without a tty, colors and backtracking / replacing existing output is impossible. So perhaps the output just needs to drop all animations and colors?

Perhaps:

• only output the tasks one by one, not all in advance
• for each task, output its text, and an ellipsis, and then "done" or an ASCII smiley or something when it's finished

E.g.

npmList ...

npmList ... done
runStandardLinter ...

npmList ... done
runStandardLinter ... done
wasteSomeTime ...

npmList ... done
runStandardLinter ... done
wasteSomeTime ... done

[jamestalmage]

Or just go verbose.

START <TASK_NAME>
task output
task output
task output
END <TASK_NAME>

If I am hunting down a problem in a Jenkins / Travis build, missing log data I suspect might be relevant is going to be a lot more frustrating than it is locally, where it is easy to rerun.

[andywer]

I guess ideally you could trigger "plain text output without control chars" and "verbose output" independently.

So it might be something like

↳ START <task>
✔ END <task>

or (if verbose)

↳ START <task>
task output
✔ END <task>

[andywer]

PS: But yes, verbose mode alone would also work for me right now 😉

[sveisvei]

Should be possible to activate with CI=true or/and LISTR_OUTPUT=simple or something along these lines.

[andywer]

listr-verbose-renderer almost does the job.

Just need a way to show all output if necessary (SamVerschueren/listr-verbose-renderer#1) and implement auto-switching to verbose renderer when in a CI scenario, piping to a file or similar.

[SamVerschueren]

Moving the discusion to #33. PR was added to add this.