[FEATURE REQUEST] Expose `supportsColor` or similar about ansis

[webdiscus]

Hallo @berstend,

thanks for the feature request.

In the v3.2.0 is added the isSupported() method that returns a boolean value.
Returning the support level value (0..3) does not make sense.

import ansis, { green } from 'ansis';

console.log(green`Color output: `, ansis.isSupported());

Grüß aus Köln

[webdiscus]

@RobinTail

it is possible, but:

1. my be a name collision when used a function with the same name in your (or others projects), because this is a "common" name
2. the named export is designed for ANSI colors and styles only, not for lib functions. This is a conscious separation.

If you wan't export the additional ansis instance, you can create one:

import { Ansis, blue, green, hex, red } from "ansis"; // <= you exports already the Ansis "class"

const ansis = new Ansis(); // <= create new instance
const color = ansis.isSupported();

Also, technically no problem, but it' not logically. I wan't mix pure ANSI names with lib functions.
E.g. the lib have the ansis.strip() method (remove ANSI codes) under ansis scope. The same works with ansis.isSupported().

[RobinTail]

I've got your point, @webdiscus , thank you.

Yes, the naming is very generic. If it was available as named export I'd most likely rename it in-place during import.

import { isSupported as isColorSupported } from "ansis"; 

But I'm okay with your vision and the suggested solution.
Thank you.

[webdiscus]

@RobinTail can the issue be closed?

[berstend]

@webdiscus wow, thanks a lot for the quick implementation 😍 👍

Gruß aus Berlin nach Köln

[RobinTail]

@RobinTail can the issue be closed?

Yes, sure, @webdiscus

[RobinTail]

can it have a named export or is that problematic, @webdiscus ?

import { isSupported } from "ansis"; // this is not available in 3.2.0