部署Angular5应用到GitHub时出现Angular CLI错误，如何解决？

Hey there! Since you didn’t share the exact error message you’re seeing, I’ll break down the most frequent issues developers face when deploying their first Angular app to GitHub using Angular CLI, plus step-by-step fixes for each.

1. "gh-pages module not found" or deployment command fails to run #

This usually happens when the required deployment tool isn’t installed. Here’s how to fix it:

• First, add the Angular CLI GH Pages deployer to your project:
  ng add angular-cli-ghpages
• If that doesn’t work, install the gh-pages dependency directly:
  npm install --save-dev gh-pages

2. 404 Errors After Deployment (Resources Not Loading) #

The #1 culprit here is an incorrect base-href setting, which tells Angular where your app is hosted relative to the domain root.

• When deploying, specify your repository name in the base-href (replace your-repo-name with your actual repo):
  ng deploy --base-href="/your-repo-name/"
• Alternatively, set it permanently in your angular.json:
  Navigate to projects -> your-project-name -> architect -> build -> options, then add:

  "baseHref": "/your-repo-name/"
  

3. GitHub Pages Doesn’t Show Your App #

Even if deployment runs successfully, you might need to adjust your repo settings:

• Go to your GitHub repo’s Settings > Pages
• Under "Source", select the gh-pages branch (this is where Angular CLI deploys your built files)
• Wait 2-3 minutes—GitHub Pages can take a bit to propagate changes, so don’t panic if it doesn’t show up instantly!

4. Production Build Fails (Before Deployment) #

If ng deploy crashes during the build step, fix the local build first:

• Run the production build command manually to see detailed errors:
  For Angular <12: ng build --prod
  For Angular 12+: ng build --configuration production
• Fix any compilation errors (like undefined variables, broken templates, or missing dependencies) before trying to deploy again.

5. Git Permission Errors #

If you get a "permission denied" message when pushing to GitHub:

• Verify your local Git is linked to your repo: git remote -v
• If not, link it with: git remote add origin https://github.com/your-username/your-repo-name.git
• Make sure you’re logged into GitHub on your machine (use git config --global user.name "Your Name" and git config --global user.email "your-email@example.com" to set your credentials if needed)

If none of these fix your issue, share the exact error message you’re getting, and I’ll help you dig deeper!

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