dabh / colors.js Goto Github PK

Since colors is taken and Marak will probably not let go of the name, how about @DABH/colors?

Never mind: I see in the other thread you're resolving this with npm. Kudos.

The issue looks to be here:
https://github.com/DABH/colors.js/blob/master/lib/system/has-flag.js#L28

Node is just loading all imports into memory like it always does, and an error shows up:

Some debugging ahead of time will show that neither argv nor process.argv are defined.

Looking for any suggestions as to what can cause this. As the dependency chain comes from winston, I would image you would be seeing more issues raised if it was a straight up bug. Thank you

Importing @colors/colors will break types (This is extremely rare --- This is the first time I have ever seen this happen)

The following code will run perfectly fine, fully type-safe. However, as soon as you import @colors/colors, it will cause an error.
Even if you import @colors/colors in a separate file (e.g inside a nested folder), it will STILL break the types!

// import colors from '@colors/colors'; // Uncommenting this line will cause the error.
// // You can also move the line to a separate file -- it will STILL cause this error.
import { z } from 'zod';

export type UnionToIntersection<U> = (U extends U ? (u: U) => 0 : never) extends (i: infer I) => 0 ? Extract<I, U> : never;
export type ArrayToIntersection<T extends readonly unknown[]> = UnionToIntersection<T[number]>;

export function arrayToIntersection<T extends readonly any[]>(arr: T): UnionToIntersection<T[number]> {
	return '' as any;
}

const tempTrash = arrayToIntersection([
	z.object({
		foo: z.object({
			one: z.string(),
		}),
	}),
	z.object({
		foo: z.object({
			two: z.string(),
		}),
	}),
]);

type TempTrash = z.infer<typeof tempTrash>;
const something: TempTrash = { foo: { one: '', two: '' } };

Other TERM values you may wish to look for:

• mintty, mintty-direct, etc.
• vt220, vt340, vt420, vt525, etc.
• tmux

Example patch:

     return 2;
   }
 
-  if (/^screen|^xterm|^vt100|^rxvt|color|ansi|cygwin|linux/i.test(env.TERM)) {
+  if (/^screen|^tmux|^xterm|^vt[1-5][0-9][0-9]|^rxvt|mintty|color|ansi|cygwin|linux/i.test(env.TERM)) {
     return 1;
   }

On any modern Linux distro (or whatever) with a reasonly up-to-date terminfo database, you should be able to get a complete list of VT100+ style TERM values via:

#!/usr/bin/env bash
toe -a | cut -f1 | while read term ; do
    if infocmp "$term" | grep -q -e 'bold=[^, ]*\E\[1m' -e 'sgr0=[^, ]*\E\[0?m' ; then
        echo "$term"
    fi
done

You probably needn't do them all, just the ones that look like they'll be reasonably common. And not all of them support color, though all should support reverse video, bold, underline, etc.

Documentation still mentions the old brightYellow style, but the interface changed to bold.yellow / yellow.bold.