Looks like readline don't always triggers keypress events on Windows

[SBoudrias]

Hi there, I'm the author on Inquirer.

I would've love to have more details to report on this bug. But I don't have much currently, I'm hoping someone would be able to help in getting more precise information. Also, due to this blindness, I can't exclude totally that this is an issue with Inquirer; all I know is these bug reports started to appear on my repo recently.

Basically, it looks like on Windows (since mostly Node 4.0), readlines don't always triggers keypress events the first time we initialize one. This have reported on Inquirer repository: SBoudrias/Inquirer.js#266

Some people the issue have said they've been able to reproduce using only a readline directly, but it's not super clear what they've done.

On my side, I've been unable to reproduce this bug on any Windows VM. So I really have a hard time to come up with reproducible step for you.

[maxdow]

Here an example to reproduce the problem :

var readline = require("readline");

var rl = readline.createInterface(process.stdin, process.stdout);

rl.on("line",function(){
  console.log("line event");
});

process.stdin.on("keypress",function(){
  console.log("keypress");
});

On a win8 computer, i don't have the keypress event triggered at first. I have to press enter to "trig" the keypress event. On win xp there is no problem, i got keypress and line events separatly.

I suppose it works the same as win xp on linux .

Inquirer.js list run fine on win xp that's why it's probably related to node

[peterblazejewicz]

same: Win: 8.1 Node: 4.1.0

[sayedihashimi]

+1 ran into this as well

[cveld]

On Windows 10 Node 4.1.0 I don't have the issue in a node session kicked off from cmd.exe. Although the Node interactive window within Visual Studio 2015 does not show any event handler activity. But my guess is that this is due the design of the Node interactive window.

[tienloc1]

On Windows 8.1 (node-v0.12.6), the keypress events work for me in cmd.exe but it still not work in git bash. (git-v2.5.3).

[dthree]

Also ran into this.

[darrellenns]

I'm also having this issue since upgrading to windows 10. Using maxdow's sample code, I get no keypress events until I press enter. Once I press enter, all the previous keypress events trigger at once. After that, keypress events trigger as normal.

I have tried this in both powershell and cmd, and I've also tried changing them to "legacy console" (in cmd/powershell preferences). All had the same behavior.

[darrellenns]

Also just tried opening node.js in a new window using the command "start node test.js". Still exhibits the same issue.