beether
commented
6 years ago I spent two hours trying to figure out why I couldn't capture color in a node process I was spawning. First of all, node is crap. You can use spawn with {stdio: 'inherit'} to preserve colors, but then you have no way of capturing the the actual f***ing output. It goes straight to stdout with no way to intercept it.
Secondly, it's astonishing that this library would forcibly disable itself with no way to prevent it from happening. Luckily, I coded the script whose output I was trying to capture, so I changed everything to chalk, which sensibly provides an env way to enable it, and I will never look back.
I just hope I'm never in the situation where I need to capture output from some process that uses colors, because I'd have no idea what to do. Hours of googling yields no results. {stdio: 'inherit'} gets me halfway there, but then I'm stuck.
Node f***ing blows.
jaredallard
givehug
DABH
I want to use | less -R with a program im using colors.js, by reading the checks in index.js there's no way to override this behaviour because the isTTY chk is done before the env var check, so the user have no choice to scroll with less.
Also, using colorized output of colors.js with less -R results in only the first line colorized, because the ansi escape codes should be done on every single line, instead of the whole string. I have workarounded this in my code, but will be good if colors.js could handle that too, this is probably a separate issue