0

I recently set up my new Window machine and tried configuring node, npm, angular-cli etc. I have done it in many machines in past and afaik I have done the same steps.

However, I have getting this strange behavior from angular cli. The ng command is recognized as can be seen from attached image, but the command is not executed. It keep throwing to me the list of methods available in cli, when I am using one of these methods.

The problem is same for all the methods.

enter image description here

I know pasting picture is not appreciated here, but in my case there is nothing else I can present.

Have anyone faced such issue ? Please suggest.

NeNaD
  • 18,172
  • 8
  • 47
  • 89
Saurabh Tiwari
  • 4,632
  • 9
  • 42
  • 82
  • Had something similar last week. Downgraded node to 14.x and npm to 6.6 (I think). Then actually installed cli in the current path separately again (even though it should have been there because of the project. So without global flag npm i @angular/cli - then everything worked again magically.. – MikeOne Feb 05 '22 at 17:08

1 Answers1

1

I had the same problem. I created this issue in the GitHub about it, and they told me that I should create a Stack Overflow question using the tag angular-cli.

So, I did it. I created this question and I even put a bounty on it. At first, I couldn't run ng command at all. Neither answer solved the problem completely, but this answer made it run. However, when I run ng command, it always just displayed all possible options to call.

Problem

This is the problem with Angular CLI v13 on Windows.

Solution

It's not much of the solution, but I downgraded the CLI to v12 and everything worked again. So I recommend this solution until someone figure out how to make it work on Windows for CLI v13.

NeNaD
  • 18,172
  • 8
  • 47
  • 89