I would be willing to make a PR for this if applicable. Thanks!

Go for it.

Start here:

and around here is where to set FORCE_COLOR:

Thanks! I'll work on it tomorrow night.

@charkour Are you in the Discord? If not, join us!

Yes! Thank you. With a different profile picture.

I had a little time to try implementing this and found that the FORCE_COLOR environment variable needs to be set in the working directory where the command is executed (for example docs). Setting it after line 487 doesn't correctly force the color.

I'll work on this more tomorrow. Let me know if you have any ideas. Go is a new language to me.

I am making good progress on this.

Is there any update on this? 🎅🎄🎁

If you're using node, you can set FORCE_COLOR=1 in your environment variables. The PR hasn't been reviewed.

@charkour Yea that's what I'm currently using, but it seems like quite a dirty solution, For example, if you have 10 packages with each of them having roughly ~4 commands

This would mean that you need to make at least 40 changes to enable colors.

I think it would be much better to use --colors, or considering the comment in your PR, the flag could be something like --node-colors instead, and eventually a unified --colors flag depending on the decisions. but yea the feature in your PR would be most welcoming. That would avoid having to set the FORCE_COLOR=1 in ~40 different places 😅