| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Review requested:
|
Sorry, something went wrong.
There was a problem hiding this comment.
tests did not play well when running in parallel. used node:test to run them sequentially
Sorry, something went wrong.
|
/CC @nodejs/util @nodejs/console |
Sorry, something went wrong.
Sorry, something went wrong.
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Sorry, something went wrong.
PR-URL: #48034 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
|
This broke tests when pulling into v18, so it needs a backport. |
Sorry, something went wrong.
|
@danielleadams It seems v18.x-staging is missing some other commits this PR depends on (b6738c1, 03db049) is that delibirate? |
Sorry, something went wrong.
|
@danielleadams cherry-picking this sequence of commits lands clearly with no conflicts and all tests pass, so I assume the staging branch is missing many many more parts 334bb17 |
Sorry, something went wrong.
|
Talked to @MoLow offline, but staging branch is ready for backport now. |
Sorry, something went wrong.
PR-URL: nodejs#48034 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
PR-URL: nodejs#48034 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
|
@MoLow Small heads up, this seems to have broken NO_COLOR support for the REPL (i.e. NO_COLOR=1 node now uses color mode when previously it didn't) |
Sorry, something went wrong.
|
@addaleax I am not able to reproduce this: |
Sorry, something went wrong.
|
@MoLow Yeah, console.log() works perfectly (its doesn't inherit colorization from the REPL), but if you enter e.g. just 111 as the input instead of console.log(111) you'll see that the output is colorized in both cases with 20.10.0, as opposed to e.g. 20.2.0 |
Sorry, something went wrong.
This was historically done to make `console.log()` have colors. However, this makes any other code that checks `process.stdout.isTTY` incorrectly assume real TTY support. Node18 and Node20 now respect `FORCE_COLOR=1` in console, so our default behavior of forcing colors in the worker process just works out of the box. See nodejs/node#48034.
| Back | FazBrowse Home | New Git URL |
The current behavior of FORCE_COLOR is to take effect when stdout/stderr are TTY's
according to the documentation:
this PR moves the check for the value of FORCE_COLOR before testing isTTY - and extracts the logic to a central utility.
Refs: #31409 (comment)