Possible node interfering with console color?

There's a whole lot of things I don't understand here, so please let me apologize in advance for this ticket as a shambles. Initially I was trying to work with a high quality console color library, and I was confounded because I had just switched to the modern Win10 console, with its 24 bit color support, and it wasn't 24 bit coloring. It's a big library by a big programmer, so I was surprised. So I thought "it's just ansi codes, I'll do it myself," and tried to do it myself. Worked them out in console printf, looked good, `node -e`, and ... and ... wha?  The same string in the same console was working with `printf` and not with `node -e console.log`. The latter was getting downgraded to a different color range. Okay, `node` must just not know it's 2-- wha?  So I tried using the `FORCE_COLOR` flag as a leader. No.  So I tried using it as an envvar. No.  So I switched to `process.stdout`. No.  And then I looked up my `TERM` setting. `xterm-color-256`. Initially I thought "aha!", except then I realized that's not the color you'd get from my testcase in a 6-cube. Oh, dear. Am I in ... am I in 4-bit color in `node`, despite having a 24-bit terminal? Wrote this to find out ```javascript const seq = n => new Array(n).fill(false).map( (_, i) => i ); const col = (r,g,b) => 16 + b + (g*6) + (r*36); seq(6).map(b => { seq(6).map(g => { seq(6).map(r => process.stdout.write(`\x1b[38;5;${col(r,g,b)}m*`) ); process.stdout.write(' '); …