Angular5项目创建失败求助：已过代理凭据安装Node及Angular5

Hey Yogi, sorry to hear you're stuck creating a new Angular 5 project even after getting Node and Angular CLI set up successfully behind your government proxy. Since you already have admin rights and worked through proxy authentication for initial installs, let's dive into the most likely fixes for this specific issue:

• Ensure Angular CLI picks up your proxy credentials
  Even if Node uses your proxy settings, Angular CLI might not inherit them automatically. Open an admin command prompt and set these environment variables temporarily first:

  set HTTP_PROXY=http://<your-proxy-username>:<your-proxy-password>@<proxy-server>:<proxy-port>
  set HTTPS_PROXY=http://<your-proxy-username>:<your-proxy-password>@<proxy-server>:<proxy-port>
  set NO_PROXY=localhost,127.0.0.1,.local
  

  For permanent setup, add these variables to your system environment variables (Control Panel > System > Advanced System Settings > Environment Variables) using your admin rights.

• Configure Angular CLI's proxy directly
  Create a .angular-cli.json file in your user directory (if it doesn't exist) and add a proxy reference:

  {
    "defaults": {
      "styleExt": "css",
      "component": {},
      "proxyConfig": "proxy.conf.json"
    }
  }
  

  Then make a proxy.conf.json file with your proxy details:

  {
    "/api/*": {
      "target": "http://<proxy-server>:<proxy-port>",
      "secure": false,
      "changeOrigin": true,
      "auth": "<your-proxy-username>:<your-proxy-password>"
    }
  }
  

  Note: If your proxy uses NTLM authentication, you'll need a tool like cntlm to handle the auth layer—Angular CLI doesn't support NTLM natively.

• Clear cached packages and reinstall Angular CLI
  Cached npm packages can cause unexpected errors. Run these commands as admin (with your proxy variables set):

  npm cache clean --force
  npm uninstall -g @angular/cli
  npm install -g @angular/cli@1.7.4
  

  Angular 5 pairs with CLI version 1.7.x, so specifying that version ensures compatibility.

• Check for firewall/endpoint restrictions
  Government networks often have strict firewalls or antivirus tools that block access to the npm registry (registry.npmjs.org). Verify this domain is whitelisted, and that your endpoint protection isn't intercepting Angular CLI's network requests.

• Confirm Node.js version compatibility
  Angular 5 requires Node.js 8.x or higher (LTS versions are most stable). Run node -v in your command prompt to check your version—if it's too old, upgrade it using your proxy credentials.

If you can share the exact error messages from your logs, I can help pinpoint the issue even more precisely!

内容的提问来源于stack exchange，提问作者yogi