-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generator doesn't respond to arrow keys in Windows 10 #8
Comments
We have seen this issue where users are not on the latest latest version of node - do you want to give that a try? |
A work around that has worked for me was to start with 'yo' and then navigate to the 'code' generator. This instead of using 'yo code' or 'yo aspnet' directly. |
This is my configuration. I think I have latest node and npm. In any case I did what @egamma suggested and was able to bypass the problem. We should probably close this issue. |
The root cause appears to be in Node v4+ (and currently still open). OmniSharp/generator-aspnet#351 Seems like Win10 folks may need to use Node 0.12 for now to use the Yeoman generator for extensions (or use the workaround from @egamma which also worked for me). |
I am on Node 5.0.0 and Windows 10. It does not work if I run the generator using |
I am on Node 5.3.0 with Windows 10. I did have the issue on 4.x until I upgraded, but now no longer have the issue. |
Thanks! |
if it doesn't wok in Git Bash, try powershell. just run the yo then select your generator |
In powershell works great. It don't works from cmd without Admin execution. |
I installed the latest version of the generator as pointed in here. After doing that the generator launches normally but I can't navigate among the various options with the arrow keys. This happens on Windows 10 environment. I don't know if it's relevant but the same happens to the asp.net yeoman generator. In OS X environment everything works file.
The text was updated successfully, but these errors were encountered: