colours

I was writing terminal CLI app and I needed colours. And I lived with the `ansi-colors` package for a bit before I got fed up with function-gated colourisation. That's not how ANSI colours should be treated. They should be treated with the respect for their domain. Coming from MUD development as I do, where we purposefully allow bleeds and compose on the fly, packages such as `ansi-colors` and `chalk` felt like padding around a thing that doesn't need it. Do you ever feel like a package maintainer created a package to solve a problem that doesn't really exist? That's how I felt. Why should I chain().functions().to().get().what().I().need()? It just felt... gross and unnecessary. ANSI needs to do what ANSI needs to do! Let it be itself!

A template literal-based ANSI colour library that just lets you write colours the way they should be written. Full 256-colour support, bold/italic/underline and friends, semantic aliases, and no function chaining in sight. Also comes with a CLI tool so you can see what you're working with. ANSI, unchained.

Domains

Tools