This article is part of my “Angular Performance Week” series, where I publish a new video each day based on the performance articles on web.dev/angular. This article focuses on how we can define performance budgets with the Angular CLI.
Note: this article and attached Egghead video lesson are based on the articles on web.dev/angular by Minko Gechev and Stephen Fluin. Full credit goes to them :thumbsup:
Angular Performance Series
- Route Level Code Splitting
- Preload Lazy Routes in Angular
- Performance budgets with the Angular CLI
- Optimize Angular’s Change Detection
- Virtual Scrolling for large lists with the CDK
- Precaching with the Angular Service Worker
Don’t miss the other videos by subscribing to my newsletter.
Configuring Performance Budgets
Measuring is extremely important, without numbers we don’t know about potential problems and we don’t have a base we can improve upon. Performance Budgets are a way to impose limits on metrics that may affect our app’s performance. In this lesson we’ll learn how to configure the Angular CLI to configure performance budgets, to monitor them and to alert us when we violate them.
Original web.dev article
Wanna read the original web.dev article? Check it out here!.