fix: Improve non-progress errors

[pgrzesik]

Non-progress error formatting (inline):

In-progress error formatting:

Details in verbose:

I also have a more general question - should we flush all final states of progresses to verbose as well? Currently, we don't do that which might be confusing to users that expect full information in verbose logs cc @mnapoli

Closes: #53

[mnapoli]

should we flush all final states of progresses to verbose as well? Currently, we don't do that which might be confusing to users that expect full information in verbose logs cc @mnapoli

Yes 💯

Actually I think what we should do is that when the Progresses is stopped (method stopAll IIRC), it should refresh one last time but this time it should write to output.stderr instead of output.interactiveStderr. I'm talking about this line specifically:

https://github.com/serverless/compose/blob/6f19215b1c69d0bb0ceb9ca75750b001567b816e/src/cli/Progresses.js#L245

That will cause:

• progress final states to be printed on stderr in case of non-interactive outputs (e.g. CI/CD)
• progress final states to be logged to the log file

This is something I wanted to address in #67 but it was even a bigger refactoring so I left it out. Feel free to tackle this!

[pgrzesik]

This is something I wanted to address in https://github.com/serverless/compose/pull/67 but it was even a bigger refactoring so I left it out. Feel free to tackle this!

I'll try to tackle this as a part of this PR 👍

[pgrzesik]

After looking a bit more into that - I think it would be better to move flushing all verbose logs from progressed outputs to file to a separate PR as I need to dive deeper into the current logic and better grasp how it's all working.