-
Notifications
You must be signed in to change notification settings - Fork 12k
PSA: if ng -v returns an error. #2462
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
Comments
I get this error:
|
Tried it multiple times. Still no success. |
Hmmm, what I did worked for windows 10. I suspect the trick is to find all the files node/npm have placed around your OS to get a true clean slate. |
@matt-erhart that's my recommendation for when ng commands stop working overall. There might be a bunch of causes for it though... I tried to gather the common ones in https://github.com/angular/angular-cli/issues?utf8=%E2%9C%93&q=is%3Aissue%20label%3A%22type%3A%20faq%22%20 . I appreciate you sharing your solution, but I can't keep this issue open as it's not actionable. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
For some unknown reason, ng commands stopped working. A lot of other people on various OSs were having a similar problem. I uninstalled npm, uninstalled node, and deleted the global node_modules folder, and installed the latest version of everything and got ng commands working again. Search for a 'complete' uninstall of npm/node to find your global node_modules folder for your OS.
The text was updated successfully, but these errors were encountered: