Angular项目构建最佳实践：通过package.json执行ng build是否合理？

Absolutely! Putting ng build (and its variant commands) into your package.json scripts is a standard, widely-recommended best practice for Angular projects—let me break down why this makes so much sense:

• Guaranteed version consistency
  When you define a script like "build": "ng build", running npm run build will always use the local Angular CLI version installed in your project's node_modules folder, not the global CLI version each team member might have installed. This eliminates frustrating issues like build failures or unexpected output caused by mismatched CLI versions across environments—critical for collaborative projects.

• Simplified, standardized commands
  No more typing out long, error-prone commands like ng build --configuration production --output-hashing all every time. You can wrap complex build flags into concise scripts, e.g., "build:prod": "ng build --configuration production", so everyone on the team uses the same exact build commands without memorizing all the parameters.

• Seamless CI/CD integration
  Almost every CI/CD tool (GitHub Actions, GitLab CI, Jenkins, etc.) plays nicely with npm scripts. By keeping your build commands in package.json, your CI config stays clean and portable—instead of configuring a custom CLI call, you just use npm run build, which works across all platforms.

• Easy extensibility
  If you need to add pre/post build steps (like cleaning the old dist folder, injecting environment variables, or running additional lint checks), you can extend the script directly. For example:

  "scripts": {
    "build": "rimraf dist && ng build",
    "build:prod": "rimraf dist && ng build --configuration production"
  }
  

  Everyone who runs npm run build will automatically execute those extra steps, no manual setup required.

Is there any scenario where this isn't ideal? #

Honestly, it's hard to think of one. Even for solo projects, this practice keeps your workflow consistent and sets you up for future scalability (if you add team members or CI/CD later). The only tiny caveat is making sure you've installed the Angular CLI locally via npm install @angular/cli --save-dev so npm can find the ng command in your project's dependencies.

Here's a typical example of how this looks in a real package.json:

"scripts": {
  "ng": "ng",
  "start": "ng serve",
  "build": "ng build",
  "build:prod": "ng build --configuration production",
  "watch": "ng build --watch --configuration development",
  "test": "ng test"
}

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