Angular 19

Angular 19 made standalone components, directives, and pipes the default for new declarations, reducing the need to mark them explicitly as standalone while retaining compatibility with NgModule-based applications. It also promoted several signal-based component APIs, including signal inputs, outputs, models, and query APIs, to stable status. Incremental hydration was introduced as a developer-preview SSR capability, allowing deferred parts of a server-rendered page to hydrate in response to defined triggers rather than all at once. The cycle also continued work on the newer application build and SSR tooling, while adding experimental reactive data APIs such as resource-style HTTP loading. Angular is not AngularJS: AngularJS is a separate, earlier framework with its own versions and its own end of life. Teams running AngularJS should use /technology/angularjs instead.

Angular 19 has reached end of life, so the Angular project no longer provides normal maintenance, security, or compatibility fixes for this line. An application can continue to run, but defects discovered in Angular 19 or its tooling must be worked around locally or accepted. The practical risk increases as supported Node.js, TypeScript, browser, RxJS, and third-party library versions move beyond Angular 19's tested compatibility range. Teams using its developer-preview or experimental features, especially incremental hydration or resource APIs, also carry upgrade risk because those APIs can change before or during adoption in later Angular versions. Remaining on 19 can therefore turn routine dependency updates, CI image changes, and browser support work into unplanned migration work.

Choose a currently supported Angular target and create an upgrade branch with the application, Angular CLI, build configuration, server-rendering code, and test suite included. Review Angular's version-compatibility requirements before changing Node.js, TypeScript, RxJS, or package-manager settings, then run the official ng update migrations for @angular/core and @angular/cli in controlled major-version steps where needed. Test production builds as well as development builds, and explicitly exercise routing, lazy loading, forms, change detection, unit and end-to-end tests, and any Angular Material components. For SSR applications, verify rendered HTML, hydration behavior, transfer-state usage, deferred views, and client-side navigation; do not assume developer-preview hydration behavior is unchanged in a newer line. Inventory NgModule and standalone boundaries, signal APIs, custom builders, and third-party packages, then replace abandoned dependencies or unsupported build integrations before cutover. Keep the Angular 19 branch only as a short-term rollback artifact, not as the maintained production baseline.