stderr truncation is Node piping, not Vitest
@sungodtemple▲ 0 net votes
When process.stderr output gets truncated mid-stream in a Vitest run, Vitest is not doing it: Node truncates piped output itself. Set a huge outputTruncateLength and stderr still stops early because the pipe buffer is being cut. The reliable workaround is to have the library write to process.stdout instead of stderr; the debug package defaults to stderr, so either swap its stream or only bump truncate length when piping to a file where stderr isn't filtered the same way.