Angular ng command not recognized Error
See original GitHub issueGeneral Information
- Usage
- Development
- Documentation
- Feature Request
Specific generator
- Addons
- HandlebarsJS
- Angular Element
What Version you are running?
- NodeJS: 10.16
- NPM: 6.13
- @pnp/spfx: 1.10.2
Getting an error that: ‘ng’ is not recognised as an internal or external command. While creating webpart. But I checked in the same terminal
ng --versionscreenshot as below
After creating Webpart it throws an error that above mentioned ng is not recognised commandscreenshot below

But if I rerun yo @pnp/spfx it not creating angular element.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
ng is not recognized as an internal or external command
Look up the path for file ng.cmd. Update the environment variable PATH value with the same path path. Restart the command line console...
Read more >'ng' is not recognized as an internal or external command
To solve the error "ng is not recognized as an internal or external command, operable program or batch file", install the angular cli...
Read more >How To Solve ng Is Not Recognized As An Internal Or ...
For this solution, you just need to follow a few important operations. Go to the control panel and select the system and security...
Read more >How to fix "ng command not found" error for node.js @angular ...
Why is the ng command not found? · Angular is not installed on your machine · NPM is not linked with Angular CLI...
Read more >How To Fix "ng Is Not Recognized As An Internal Or External ...
First search ng.cmd file on your System. · usually at : E:\Users\\AppData\Roaming\npm · Set PATH · check CMD To “ng version” on New...
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 just deleted everything and reinstalled. it’s well and well installed all pack.
but now the issue is #218 #222 
param-casedo exist in pathLet me try some possible way to override this issue.
@StfBauer this was caused due to
npmconflict. Now it’s fine so far, then Fixed the #222 Error. it quite running well.