I’m having trouble with npm on a fresh Windows 10 setup. I’ve got Cygwin installed for Unix commands in cmd.
When I run npm install -g @angular/cli, it starts downloading but then fails with a certificate error:
gyp ERR! configure error
gyp ERR! stack Error: unable to get local issuer certificate
// ... (error message shortened)
I tried editing the npm config file and added:
strict-ssl=false
http_proxy=null
proxy=null
But no luck. The error persists, and even basic npm install commands fail now. Any ideas on how to fix this? I’m stuck and can’t move forward with my Angular project setup.
hey mate, had similar probs. try this: download the Angular CLI package manually from npm’s website. then use ‘npm install -g’ with the file path. also, make sure ur running cmd as admin. if that don’t work, maybe try a diff network? sometimes corp networks mess with npm. good luck!
I encountered a similar issue when setting up Angular on a new Windows machine. The certificate error was often due to interference from corporate networks or antivirus software. One approach that worked for me was to run the command npm config set strict-ssl false in the command prompt. Alternatively, setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable by executing set NODE_TLS_REJECT_UNAUTHORIZED=0 can help. Updating npm and Node.js to more recent versions also resolved certificate issues in my setup. As a final troubleshooting step, manually downloading and installing the Angular CLI package proved successful. Remember to revert any security changes after installation.
I hope this information helps you overcome the issue.
I’ve dealt with this frustrating certificate issue before. One thing that worked for me was clearing the npm cache completely. Try running ‘npm cache clean --force’ in your command prompt, then attempt the installation again.
If that doesn’t do the trick, you might want to check your system’s date and time settings. Believe it or not, incorrect system time can cause certificate validation failures.
Another approach is to temporarily disable your antivirus software during the installation process. Some overzealous AV programs can interfere with npm’s ability to verify certificates.
Lastly, if you’re behind a corporate firewall, you may need to configure npm to use your company’s certificate authority. This usually involves setting the ‘cafile’ config option to point to your organization’s CA certificate.
Hope one of these solutions helps you get past this roadblock!