Open MSLaguana opened 8 months ago
The @web/test-runner-core package includes the TestRunnerCli class, which always has a DynamicTerminal that it references that has no knowledge of the staticLogging configuration variable. The TestRunnerCli will do things like decide not to print progress, but the DynamicTerminal will always try to clear the console via https://github.com/modernweb-dev/web/blob/master/packages/test-runner-core/src/cli/terminal/DynamicTerminal.ts#L133
TestRunnerCli
DynamicTerminal
staticLogging
This means that in non-interactive scenarios like CI, the output will have ansi codes embedded in it with no way to disable it (without drastic measures like monkey patching process.stdout.write) that i can find.
process.stdout.write
The @web/test-runner-core package includes the
TestRunnerCliclass, which always has aDynamicTerminalthat it references that has no knowledge of thestaticLoggingconfiguration variable. TheTestRunnerCliwill do things like decide not to print progress, but theDynamicTerminalwill always try to clear the console via https://github.com/modernweb-dev/web/blob/master/packages/test-runner-core/src/cli/terminal/DynamicTerminal.ts#L133This means that in non-interactive scenarios like CI, the output will have ansi codes embedded in it with no way to disable it (without drastic measures like monkey patching
process.stdout.write) that i can find.