Disable colors for non-interactive output

[c0d3d]

What did you implement:

Closes #480

How did you implement it:

Check if stdout is a tty when deciding to use colors or not.

How can we verify it:

1. Run from tty (interactive shell) to see default still has colors
2. Pipe into a file to see that it doesn't write colors.

Todos:

• Write tests
• Write documentation
• Fix linting errors
• Make sure code coverage hasn't dropped
• Provide verification config / commands / resources
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES
Is it a breaking change?: NO

[c0d3d]

@HyperBrain Can you look at this? Would help our Jenkins build from looking awful.
Thanks!

[hassankhan]

Perhaps I'm missing something, but it doesn't seem like the tty package is in the project's package.json?

Disregard 😄

[c0d3d]

@hassankhan Can you help get this merged?
Would make my Jenkins output much better :D

[hassankhan]

@c0d3d Unfortunately I don't have write access to the repo, I would love to see this PR merged for the same reason 👍

@HyperBrain is there anything I can do to help get the PR merged in? 😄

[HyperBrain]

@hassankhan I just invited you to the serverless-webpack-team. You should have write access as soon as you confirm the request ;-)

[hassankhan]

Thanks for the invite @HyperBrain 😄

If there's no other issue with the PR, is it cool to go ahead and merge it? Or is there any other process I should be following aside from code-review + passing tests?

[HyperBrain]

No, that should be ok. However, it is important to have the milestone set properly on the PR and the issue, so that I can create a proper changelog for the next release

…

On Sun, Apr 7, 2019 at 7:22 PM Hassan Khan ***@***.***> wrote: Thanks for the invite @HyperBrain <https://github.com/HyperBrain> 😄! If there's no other issue with the PR, is it cool to go ahead and merge it? Or is there any other process I should be following aside from code-review + passing tests? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#481 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFRM3nCMY8vJVqC9fXcm4F6QxozHM1HBks5veilVgaJpZM4aadMA> .

[hassankhan]

Thanks for creating the PR @c0d3d, should be released in v5.3.0 👍