David Hyde

@Marak , It looks like you removed me from this repo so I'm unable to help. I can only imagine everything you're going through right now, but there are a...

**Folks, a quick update.** Semi-official since I have been a maintainer on this project for 2 or 3 years (albeit largely passively). 1. Active steps are being taken to resolve...

**All**: The latest status update is still https://github.com/Marak/colors.js/issues/285#issuecomment-1008212640 , i.e., pin at 1.4.0, use `@dabh/colors`, or wait till tomorrow for updates. Please try to avoid adding unnecessary comments (even lighthearted...

This is a duplicate of #285 . For sake of making solutions easy to find, please consider closing this issue so folks go to #285 instead. Thanks.

If you read #285 you’ll see I’ve already forked and am working to resolve the incident with the relevant parties.

Is this a colors issue or a vscode issue? https://github.com/Microsoft/vscode/issues/45572

Interesting; we should investigate the order in which ANSI codes are emitted (seems like we're doing it a bit backwards eh?). I'm not sure if there are any unintended consequences...

Thanks for investigating @jpike88 ! I've recently started triaging and going through all the issues and PRs -- things have already been cleaned up quite a bit in the past...

Is there some reason orange isn't always supportable? See comments at bottom of #123 ... generally this seems like it should be merged, but feels like a little extra clarity...

Orange is not an ANSI color, would something like #76 be preferred? (Just all-out support custom colors... why stop at orange...)