Netlify Ships Same-Day Support for Angular v22 With Automatic Host and Header Config.

Netlify announced same-day support for Angular v22, releasing version 4.0.0 of its Angular runtime to handle two breaking changes that would otherwise disrupt deployments on the platform.

Angular v22, released by Google today, introduces a stricter allowedHosts configuration option that returns HTTP 400 errors for any hostname not explicitly whitelisted. The update also requires applications behind reverse proxies to enable trustProxyHeaders to correctly read forwarded headers like X-Forwarded-For and X-Forwarded-Proto. Both settings would normally require manual configuration from developers shipping Angular apps on Netlify.

The new runtime release wires up both automatically. Branch previews and deploy previews work without additional configuration, and forwarded headers are handled for applications running behind Netlify's infrastructure.

Angular v22 raises the minimum Node.js version to 22.12.0. Developers deploying on Netlify will need to configure their build to use a supported Node.js version before upgrading.

The allowedHosts option, first introduced in Angular v21.x via @angular/ssr, gave developers explicit control over which hosts could connect to their applications. In v22, Angular started enforcing this list by returning HTTP 400 responses for any request with a host header not on the list. For platforms like Netlify that generate unique URLs for each branch and deploy preview, this would mean developers manually adding every preview URL to the config.

Netlify's runtime now injects the most common Netlify URLs into the allowedHosts configuration automatically, eliminating the HTTP 400 errors that would otherwise block preview deployments.

The trustProxyHeaders setting addresses a separate but related issue. Applications deployed behind reverse proxies, like those on Netlify, need to trust forwarded headers to correctly identify client IPs, protocols, and original request details. Without this setting enabled, Angular apps would misinterpret request metadata. The v4.0.0 runtime enables this by default for Netlify deployments.

Developers running Angular apps on Netlify should follow the official Angular upgrade guide and update @netlify/angular-runtime to version 4.0.0 or later. The runtime is available via npm and handles the host and header configuration without requiring changes to application code.

Netlify maintains framework-specific runtimes for Angular and other major frameworks, abstracting platform-specific deployment requirements. The company has recently expanded its developer tooling, including prompt-to-deploy workflows and AI-powered development features.

The full changelog and upgrade notes are available in the Netlify Angular Runtime repository.