eslint --init remains stuck at "Are you using ECMAScript 6 features?" under Node 8.1.0
See original GitHub issueEnvironment
- ESLint: 3.19
- Node: 8.1.0
- npm: 5.0.3
- OS/Terminal: Bug happens under both:
- Ubuntu 16.04.2LTS / GNOME Terminal 3.18.3 / {zsh 5.3.1, bash 4.3.48}
- Windows 7 / cmd
Reproduction steps
~ npm install eslint
~ ./node_modules/.bin/eslint --init
? How would you like to configure ESLint? Answer questions about your style
? Are you using ECMAScript 6 features? (y/N)
What did you expect to happen?
Be able to type y/n
What actually happened?
- Typing produces nothing visible on screen.
- It is impossible to quit the assistant; Ctrl+C / Ctrl+D don’t respond. I have to kill the terminal.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Node 8.1 breaks Inquirer.js: Hangs on nested calls · Issue #547
eslint --init remains stuck at "Are you using ECMAScript 6 features? ... The cli generator hangs on nested questions when using node 8.1.0...
Read more >Language Options - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >eslint | Yarn - Package Manager
ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and...
Read more >eslint - npm.io
ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and...
Read more >ESlint Error Install from Command Line - Stack Overflow
It looks like you're trying to install globally while your user doesn't have access to the global node_modules ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This should be fixed in Node 8.1.1, which was released today.
Just a me-too, I had this problem on OS X with node v8.1.0, fixed in 8.2.1 (Homebrew).