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
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
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 rundeno 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
