only do process.stderr.write on a Windows TTY stream

lib/verbose/log.js

@@ -1,4 +1,5 @@
 import process from 'node:process';
+import {writeFileSync} from 'node:fs';
 import {inspect} from 'node:util';
 import {escapeLines} from '../arguments/escape.js';
 import {defaultVerboseFunction} from './default.js';
@@ -9,7 +10,14 @@ export const verboseLog = ({type, verboseMessage, fdNumber, verboseInfo, result}
 	const verboseObject = getVerboseObject({type, result, verboseInfo});
 	const printedLines = getPrintedLines(verboseMessage, verboseObject);
 	const finalLines = applyVerboseOnLines(printedLines, verboseInfo, fdNumber);
-	process.stderr.write(finalLines);
+	// On Windows when stdout is pointing to a terminal writeFileSync causes problems with multibyte Characters not displaying correctly
+	// When stderr is pointing to console, the write command is allway behaving synchronously
+	if (process.platform === 'win32' && process.stderr.isTTY) {
+		process.stderr.write(finalLines);
+		return;
+	}
+
+	writeFileSync(STDERR_FD, finalLines);
 };
 
 const getVerboseObject = ({
@@ -35,6 +43,9 @@ const getPrintedLine = verboseObject => {
 	return {verboseLine, verboseObject};
 };
 
+// Unless a `verbose` function is used, print all logs on `stderr`
+const STDERR_FD = 2;
+
 // Serialize any type to a line string, for logging
 export const serializeVerboseMessage = message => {
 	const messageString = typeof message === 'string' ? message : inspect(message);