`au new` get stuck after the first question
See original GitHub issueI’m submitting a bug report
- Library Version: 0.30.0
Please tell us about your environment:
-
Operating System: Windows 10 (15063)
-
Node Version: 8.1.0
- NPM Version: 5.0.3
-
Browser: all
-
Language: all
Current behavior:
After answering the first question of au new
or au new some-name
PowerShell doesn’t accept any input (including ctrl + c). Tried some other terminals, but same behaviour. It works on other machines (but other OS versions). Haven’t tested on an other machine with the same Windows version.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Retained tampon or other object - Healthdirect
A tampon is 'retained' when the tampon has been inserted but later becomes either stuck or 'lost'. Reasons for this may include: putting...
Read more >If your Mac starts up to an Apple logo or progress bar
When you're updating or upgrading macOS, the Apple logo or progress bar may persist for much longer than usual. As the installation process ......
Read more >Troubleshooting for your catheter - HealthyWA
This information applies only to suprapubic or indwelling urinary catheters. This is called bypassing and happens when the urine cannot drain down the...
Read more >Australia needs workers but a million are stuck at the door
A blowout in visa processing times has left about a million prospective workers stuck in limbo.
Read more >Ipython console in Spyder stuck on "connecting to kernel"
I can also quit the kernel from this new IPython console but this does not solve my problem because when I launch a...
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 Free
Top 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
I can confirm that it started to work with nodejs 8.1.1.
I’d recommend to downgrade to v8.0.0 @arabsight and @Lichtjaeger