Swap chalk for turbocolor.

[jorgebucaran]

Hello webpack-cli maintainers! 👋

This PR basically swaps chalk for Turbocolor.

---

What kind of change does this PR introduce?

Swaps one library for another that uses the same API, but it's lighter (no deps) and has significantly better load/runtime performance (~>20x faster).

Did you add tests for your changes?

Same tests pass, so should be good.

If relevant, did you update the documentation?

I did, is it good?

Summary

It should give you a small perf boost as turbocolor loads >20x faster and applies styles >18x faster than chalk for the same API (see benchmarks). Node.js >=v4 supported.

# Load Time
chalk: 15.190ms
turbocolor: 0.777ms

# All Colors
chalk × 8,729 ops/sec
turbocolor × 158,383 ops/sec

# Chained Colors
chalk × 1,838 ops/sec
turbocolor × 39,830 ops/sec

# Nested Colors
chalk × 4,049 ops/sec
turbocolor × 59,833 ops/sec

Does this PR introduce a breaking change?
No!

---

Let me know if this is acceptable to you and if I need to change anything. Cheers!

[jsf-clabot]

All committers have signed the CLA.

[webpack-bot]

@jorgebucaran The most important CI builds failed. This way your PR can't be merged.

Please take a look at the CI results from travis (failure) and fix these issues.

[evenstensberg]

Hi @jorgebucaran, thanks for the attention and PR!

I'm going to ask the team first, let me get back to you once we're decided!

[jorgebucaran]

Hi @ev1stensberg, thanks sounds good :)

[ematipico]

Any comparison regarding the sizes of the packages?

[jorgebucaran]

@ematipico I usually go to bundlephobia to find out:

• chalk@2.4.1 — 20.2 kB (7.5 kB min+gzip)
• turbocolor@2.2.0 — 1.1 kB (695 B min+gzip)

[evenstensberg]

@jorgebucaran any difference between the two packages? API wise ?

[jorgebucaran]

@ev1stensberg Feature-wise chalk has more options, but webpack-cli is using none of them and some of those options are not widely supported by terminals. API-wise, they're virtually the same, but let's see one thing.

Chalk supports variadic arguments like:

console.log(chalk.red("Hello", "World"))

...whereas turbocolor is a unary function by design. (There are so many ways that arguments can cause a function to be unoptimizable.)

console.log(color.red("Hello" + "World"))

// or 

console.log(color.red("Hello %s"), "World")

// or

const name = "World"
console.log(color.red(`Hello ${name}`))

You can see all the features supported by turbocolor in the usage section.

---

Hope that answers your question :)

[webpack-bot]

Hi @jorgebucaran.

Just a little hint from a friendly bot about the best practice when submitting pull requests:

Don't submit pull request from your own master branch. It's recommended to create a feature branch for the PR.

You don't have to change it for this PR, just make sure to follow this hint the next time you submit a PR.

[evenstensberg]

Hi @jorgebucaran . Me and my team have discussed a bit, and we don't really see the point of swapping chalk for another library. Chalk is stable and good enough for us as of this date. Thanks for the PR 👍

[jorgebucaran]

@ev1stensberg No problem! Cheers!