Roadmap ideas

Here are the goals for Chalk 3:

• Drop support for Node.js 4
• Bundle all dependencies at publish-time. I would usually never do this, but Chalk is one of the most popular packages on npm. We could use Browserify or Webpack something to make it a single file.
• require('chalk/lite') which only includes support for 16-bit. For when you need something fast and simple for logging.
• Move to class-based construction: #188
• Improve speed, both require speed (#180) and execution speed (https://github.com/chalk/chalk/issues/333). For execution speed we could add fast-paths for when only using 16 colors, which is the most common use-case.
• Stop using the color-convert module. It’s too slow and flexible. We don’t really need that many ways of specifying colors. I would prefer to support just keywords, HEX, RGB. I’m honestly not sure if this is feasible. Just an idea for improving the package size and performance. Alternatively, make color-convert tree-shakable, so we only get the parts we actually need.
• Browser DevTools support built-in? This has been a common request and as long as it doesn’t require too much code (and no new dependencies), I welcome a PR adding it.

We welcome contributions to help with this effort and ideas for the v3 goals. 🙌

---

@Qix- Thoughts? Anything else?

[sindresorhus]

Any interest in rewriting it in Flow?

No, I’m used to TypeScript and prefer that.

[callumlocke]

I’m open to someone rewriting Chalk in TypeScript if they also do #188.

Any interest in rewriting it in Flow? Either way it would be good to provide out-of-the-box type definitions for both TypeScript and Flow.