How do you keep an Angular application's JavaScript budget under control?

Budgets are layered: initial JavaScript and CSS, notable lazy features, individual component styles, and sometimes a baseline percentage for regression control. I validate on representative devices and networks because the same kilobytes have different impact depending on execution cost and caching. Dependency upgrades are reviewed for both size and runtime behavior. Observability connects releases to loading metrics so the budget remains a product constraint rather than a ceremonial CI rule.