Cannot use arrow keys to choose options on `eslint --init` on Windows

What version of ESLint are you using? v2.6.0 What parser (default, Babel-ESLint, etc.) are you using? none yet Please show your full configuration: none yet What did you do? Please include the actual source code causing the issue.

filipe.silva@DESKTOP-7ND6T3R MINGW64 ~
$ npm install -g eslint
(...)
filipe.silva@DESKTOP-7ND6T3R MINGW64 ~
$ eslint --init
? How would you like to configure ESLint? (Use arrow keys)
> Answer questions about your style
  Use a popular style guide
  Inspect your JavaScript file(s)

What did you expect to happen? Expected to be able to choose second option using arrow keys. What actually happened? Please include the actual, raw output from ESLint. Could not choose any option using arrow keys on the first prompt. Subsequent prompts I was able to use arrow keys.

This happened on a win10 system, using both gitbash and cmd.

[platinumazure]

I think as a workaround, you can use numbers plus the Enter key. There’s one question where it says use a space to select (Node vs Browser), in which case the sequence is something like 2-space-enter.

Unintuitive, I know, but it might get you on your way. (I’m using Windows 7, though, so maybe not.)

[jokeyrhyme]

I have a module that helps identify broken versions of Node:

• https://github.com/jokeyrhyme/is-node-interactive-tty-broken

Do you think it might be worth integrating a similar check into this library? So that a warning or something could be displayed? Or perhaps modifying the “engines” part of package.json to help avoid broken Node versions at installation time?