Issues with ANSI control codes on compiled EXE
After updating Deno from a 2.2.x series update (not sure exactly which), I've got what seems to be a regression with deno compile.
I'm using the yoctocolors and inquirer npm packages for a basic CLI tool, both of which have worked perfectly up to this point. After updating, the output from
deno run seems normal (see attached).
However, when the program is compiled, it now seems like the ANSI escape codes are being directly written out to the screen.
The program is running on a Windows Server 2022 box, which means it does not come with the new OpenConsole or Windows Terminal from more recent OS versions, and I've found that manually installing Windows Terminal and running via that works normally - but this was working with a compiled exe on the previous Deno version without issue, so my assumption is that there is some regression with Deno which is causing this.
Can anyone shed some light here? Happy to provide more details as needed
3 Replies
Worth mentioning, I'm on Deno 2.3.7 now, but was able to reproduce the issue on canary.
The issue disappears when downgrading to 2.2.5. When moving to 2.2.6 it reappears.
I'm able to reproduce this issue with the
color_logging example from the deno docs:
As this seems to be a regression between versions, I have also opened a bug report on GH - https://github.com/denoland/deno/issues/29875
GitHub
Incorrect ANSI control code output on console.log when using deno c...
Version: Deno 2.2.6+ Description A regression on console output on systems running Windows Server 2022 (and possibly others which are not using the new Windows Terminal) appears to have been introd...