-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng --version errors without node_modules dir #10917
Comments
I am getting that same error:
The only cause I can think of is of mixing both I have been unsuccessfully trying to upgrade from angular 5 to angular 6. Now I am trying to do a fallback. Nothing is working |
I am getting this error on my WIndows dev box when calling |
I have the same problem, but the error message is different. In my case, @angular/cli was installed globally with yarn instead of npm. This command is run from VSCode terminal window. Is this a powershell compatibility issue?
It does work from within cygwin or the windows command prompt
Should this be reported in a separate bug report, related to powershell compatibility? |
I had the same issue and solved it by changing to the root directory [ |
This happens in yarn 2 plug-n-play set ups as well, because there's no longer a |
Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version. If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. |
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. |
Versions
Repro steps
Using GitLab CI:
Observed behavior
Desired behavior
I would expect version information to be given even if there is not a node_modules/ directory present
Mention any other details that might be useful (optional)
The text was updated successfully, but these errors were encountered: