[Windows] Exiting a running bun process with Ctrl + C messes up the cmd command history

[moruzerinho6]

What version of Bun is running?

1.1.0

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What steps can reproduce the bug?

function sleep(ms) {
  return new Promise(resolve => setTimeout(resolve, ms));
}

(async () => {
  console.log('Running...')
  await sleep(10000)
  console.log('Passed.')
})()

What is the expected behavior?

While the process hasn't finished executed, if you force exit by pressing Ctrl + C and then press the up arrow to get the last command that was executed, a unrelated sequence of characters will be provided instead, such as ^[[A

Video examples:

What do you see instead?

After exiting a running process and pressing the up arrow, the last executed command should be provided, for those that don't use something like nodemon or watch mode this is extremely important to quickly run the last command again.

Video example:

unknown_2024.04.04-16.51_1.mp4

Additional information

If you continue to press the up arrow you'll constantly get the same string again and again.

[moruzerinho6]

Still happens with v1.1.1

[moruzerinho6]

More context, this only happens when using Windows CMD, it works as expected when using Windows PowerShell.

[techroy23]

I'm running the latest version of bun and this still happen.