Repository navigation
https://github.com/nodejs/node/pull/54677 should be backported to NodeJS 20 Branch #55726
Closed as not planned
Description
Version
v20.18.0
Platform
No response
Subsystem
No response
What steps will reproduce the bug?
This #54677 is not implemented in v20.18.0
v18.20.4 and v22.11.0 (other LTS) versions have console.error not red
How often does it reproduce? Is there a required condition?
Every time
What is the expected behavior? Why is that the expected behavior?
This #54677 should be implemented for v20.x
same behavior as v18.20.4 and v22.11.0 (other LTS) versions
What do you see instead?
console.error is red in v20.18.0
node -e "console.error(process.version)"
is v20.18.0 and red
Additional information
The code that should be reverted first appeared in NodeJS 20 branch in v20.15.0
Activity
[-]Revert https://github.com/nodejs/node/pull/54677 in NodeJS 20 Branch[/-][+]Backport https://github.com/nodejs/node/pull/54677 to NodeJS 20 Branch[/+][-]Backport https://github.com/nodejs/node/pull/54677 to NodeJS 20 Branch[/-][+]https://github.com/nodejs/node/pull/54677 should be backported to NodeJS 20 Branch[/+]avivkeller commentedon Nov 5, 2024
SGTM, just gotta wait for the next LTS release, and if it's not clean, open a backport PR
avivkeller commentedon Nov 18, 2024
Fixed by #55879
github-actions commentedon Apr 26, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon May 26, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.