Angular › Build, Environments & Deployment

Why is it important to set a bundle size budget in an Angular project's configuration?

Beginner

Answer

A bundle size budget warns or fails the build if your app's JavaScript files grow beyond a specified size, helping the team catch accidental bloat, such as an unnecessarily large library being added, before it slows down the app for real users on slower connections.
// angular.json
"budgets": [
  { "type": "initial", "maximumWarning": "500kb", "maximumError": "1mb" }
]
Real-world example A team catches an accidental increase in their app's bundle size right during a pull request, since the build fails with a clear budget warning before the change is ever merged and deployed to real users.

Common follow-ups: What is the difference between the initial bundle and lazy loaded bundles when it comes to budgets?;How do you decide on an appropriate budget size for a specific app?