@iansan5653 first of all thanks for your PR.
Overall it looks good. I have left some comments directly in the code. Please address those and than we can look into merging this PR.

Also have you tested that this fixes this issue
@DanTup since it is your issue originally, can you checkout this PR and verify your issue gets fixed? Thanks

Thanks a lot!

@iansan5653 this is good work.
However this week we are in endgame which means we only take a limited set of changes before we release.
Bottom line: I will merge this in next week and it will be available as part of the April release in more than a month.

I had a quick test of this, and it seems like the foreground works, but the background does not.

For ex., this node coed:

const t1 = "\x1B[32m       test   \x1B[0m";
const t2 = "\x1B[38;5;2m   test   \x1B[0m";
const t3 = "\x1B[42m       test   \x1B[0m";
const t4 = "\x1B[48;5;2m   test   \x1B[0m";
console.log(t1);
console.log(t2);
console.log(t3);
console.log(t4);

Looks like this in the terminal:

But like this in the Debug Console:

(I'm not sure if it's expected that the colours are slightly different too?)

@iansan5653 can comment on that one @DanTup

@DanTup That's odd; I'll look into it.

As far as the colors being slightly different, that should be solved by #70969.

@DanTup Can you try it now? I had overlooked a comparison when I changed the isForeground boolean to the colorType string.

Looks like that also fixed a failing test I had so the build is only failing due to an unrelated issue with the main codebase.

LGTM, thanks!

@DanTup thanks for verifying
@iansan5653 yes the build fails due to unrelated errors.

Let's keep this as is and I will merge next week. Thanks!

Here's a full test file in case anyone wants to try it themselves.
https://gist.github.com/iansan5653/c4a0b9f5c30d74258c5f132084b78db9