Angular 17

Angular 17 made standalone APIs the default for newly generated applications, reducing the need for NgModules in new code. It introduced built-in template control-flow syntax such as @if, @for, and @switch as a developer-preview alternative to structural directives, along with deferrable views using @defer for splitting and loading template blocks later. Signals became stable, providing a supported reactive state primitive. The cycle also added a new application build system based on esbuild and Vite in developer preview, and made client hydration for server-rendered applications stable. These features changed recommended patterns, but several of the newer build and template capabilities needed careful validation before broad production adoption. 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 17 has reached end of life, so Angular no longer provides maintenance releases or security fixes for this cycle. Remaining on it leaves defects in the framework, CLI, compiler, server-side rendering stack, and supported dependency combinations unresolved. The practical risk grows as supported Node.js, TypeScript, browser, package-manager, and testing-tool versions move forward: dependency upgrades may become blocked by Angular 17 compatibility limits, while keeping older tools can introduce separate security and operational problems. Applications that adopted developer-preview features in this cycle may also face migration work because later Angular releases can refine their APIs, build behavior, or generated output.

Plan an upgrade to a currently supported Angular release rather than treating Angular 17 as a long-term platform. Inventory the installed versions of @angular/core, @angular/cli, Angular Material, TypeScript, RxJS, Node.js, test runners, and build integrations, then use the Angular update guidance and schematic migrations for each required major-version step. Upgrade and test in a branch or representative application first, especially custom builders, SSR and hydration setups, Angular Material usage, browser support, unit and end-to-end tests, and CI images. If the application uses @if, @for, @switch, @defer, signals, or the newer application builder, verify behavior and performance on the target release rather than assuming preview-era behavior is unchanged. Remove obsolete workarounds and keep framework and CLI versions aligned before rolling the upgrade through production environments.