Inconsistent console.log behavior with carriage return \r between Node.js and browsers

[islandryu]

Version

v23.0.0

Platform

Darwin shimaryuuheinoMac-mini.local 24.0.0 Darwin Kernel Version 24.0.0: Mon Aug 12 20:52:12 PDT 2024; root:xnu-11215.1.10~2/RELEASE_ARM64_T6020 arm64

Subsystem

No response

What steps will reproduce the bug?

$ node
Welcome to Node.js v23.0.0.
Type ".help" for more information.
> console.log('foo\rbar')

How often does it reproduce? Is there a required condition?

consistently

What is the expected behavior? Why is that the expected behavior?

output foobar

What do you see instead?

Node: bar
chrome,safari, edge: foobar

Additional information

I believe this is the expected behavior of standard output, but the difference from how it behaves in browsers left me feeling a bit confused.

[RedYetiDev]

console.log sends the output to the terminal. How the terminal handles that data is out of Node.js's control.

Most terminals handle \r as you've described, moving the cursor back to the beginning of the current line.