Cursor rendering artifact bug when using node.js under terminal

[sixtram]

When I use Node.js REPL in Windows Terminal (in a standard Windows command prompt tab), I sometimes get another cursor rendered one line below the current position. Node.js normally evaluates the current expression while I'm typing, and this additional cursor appears there. This doesn't happen in the standard Windows command prompt.

Here is a screenshot to illustrate. If I type the expression to evaluate, but don't hit the Enter key, but move the cursor back and forth, an extra cursor appears for a few milliseconds. Hard to screencapture, but it appears at the tip of the red arrow.

[sixtram]

Actually, node.js does the same in the standard windows command prompt, so it's not an issue with windows terminals.