Netlify Changelog - Framework

Angular v22 is now supported

Wed, 03 Jun 2026 00:00:00 GMT

Angular v22 was released today and it is supported on Netlify on day one. To upgrade, follow the Angular upgrade steps and update @netlify/angular-runtime to v4.0.0 or later. Notable changes

Minimum Node.js version: Angular v22 requires Node.js 22.12.0 or later. Make sure your Netlify site is configured to use a supported Node.js version .
allowedHosts config: Angular v21.x (specifically, @angular/ssr) introduced an allowedHosts option in the AngularAppEngine configuration, giving you explicit control over which hosts are permitted to connect. Angular 22 started returning a HTTP 400 for requests with other host headers. @netlify/angular-runtime handles adding the most common URLs for a Netlify deploy to the allowedHosts config automatically allowing developers to use Netlify's branch and deploy previews without the HTTP 400 error.
Forwarded headers support withtrustProxyHeaders: A new trustProxyHeaders option lets Angular applications behind a reverse proxy correctly read forwarded headers such as X-Forwarded-For and X-Forwarded-Proto. @netlify/angular-runtime handles adding the required headers automatically.

Learn more:

Angular v22 Release
Angular on Netlify
Angular Runtime

Hydrogen with React Router 7 now supported on Netlify

Tue, 24 Mar 2026 00:00:00 GMT

Shopify's Hydrogen framework now works on Netlify with React Router 7 and Hydrogen 2026.1.0. The Netlify Hydrogen template has been fully rebuilt, and @netlify/vite-plugin-react-router now supports Hydrogen sites out of the box. The updated template also comes with two meaningful improvements:

Netlify Cache API integration — Data fetching is cached using the Netlify Cache API , giving you low-latency responses without extra configuration.
Full local platform emulation — The Netlify Vite Plugin provides zero-config local emulation of Blobs, Functions, Edge Functions, and AI Gateway during development, so what you test locally matches what runs in production.

To get started with a new Hydrogen site on Netlify, deploy the updated template: Deploy to Netlify To move an existing Hydrogen site over to Netlify, follow the How to deploy a Shopify Hydrogen storefront to Netlify guide. Learn more:

Hydrogen template on GitHub
@netlify/vite-plugin-react-router v3.1.0 release notes
How to deploy a Shopify Hydrogen storefront to Netlify

Astro 6 just works on Netlify

Tue, 10 Mar 2026 00:00:00 GMT

Astro 6 is out today, and it just works on Netlify on day one. To upgrade, run: npx @astrojs/upgrade This will update Astro, the Netlify adapter, and all other official integrations together. What's new Some highlights include:

Vite 7 and a redesigned dev server — Faster builds and a better dev server built from the ground up.
Content Layer API — Legacy content collections are fully removed. All collections must now use the Content Layer API .
Node 22 — Node 18 and 20 are no longer supported.

Check the full upgrade guide for all the details. Watch out for import.meta.env One change worth calling out: import.meta.env values are now always inlined at build time in Astro 6. This means if you were relying on import.meta.env to read environment variables at runtime in your server-side code, those values will be baked into your build output instead. To read environment variables at runtime, use process.env instead: - const apiKey = import.meta.env.API_KEY; + const apiKey = process.env.API_KEY; This is especially important for secrets. If a secret is inlined into your server bundle, it's no longer secret. The good news: Netlify's smart secret scanning will automatically detect exposed secrets in your build output and fail the build before it goes live, so you'll know right away if something slipped through. Deploy an Astro 6 site on Netlify If you want to get started with a new site, start with the Astro on Netlify doc, or just click this button: Deploy to Netlify

Security Update: Multiple vulnerabilities in SvelteKit

Thu, 15 Jan 2026 00:00:00 GMT

The Svelte team has disclosed five CVEs affecting the Svelte and SvelteKit ecosystem. Here's what Netlify customers need to know. Vulnerabilities

CVE-2026-22775 : Memory/CPU exhaustion in devalue (5.1.0–5.6.1)
CVE-2026-22774 : Memory exhaustion in devalue (5.3.0–5.6.1)
CVE-2026-22803 : Server crash in @sveltejs/kit (2.49.0–2.49.4)
CVE-2025-67647 : Server crash and SSRF in @sveltejs/kit (2.44.0–2.49.4) and @sveltejs/adapter-node (2.19.0–2.49.4)
CVE-2025-15265 : XSS in svelte (5.46.0–5.46.3)

Impact on Netlify CVE-2026-22775, CVE-2026-22774, and CVE-2026-22803 These are server-side denial-of-service (DoS) vulnerabilities. On Netlify, these have minimal impact: our autoscaling serverless architecture means that a malicious request resulting in a crashed or hung function does not affect other requests. However, active exploitation could increase your function costs. In addition, note that only sites using the experimental Remote Functions feature are affected. CVE-2025-67647 As above, this DoS vulnerability involves intentionally "crashing" a server. On Netlify, this has minimal impact. The SSRF vulnerability affects a @sveltejs/adapter-node, which is not used by apps deployed to Netlify. CVE-2025-15265 This is a client-side cross-site scripting (XSS) vulnerability. Regardless of hosting provider, all apps using the experimental hydratable with unsanitized user-controlled keys are vulnerable. What should I do? Although the impact to Netlify sites is limited in this case, we always strongly recommend upgrading as soon as possible to patched releases:

devalue 5.6.2 or later
@sveltejs/kit 2.49.5 or later
@sveltejs/adapter-node 5.5.1 or later
svelte 5.46.4 or later

Resources

Svelte team disclosure

Angular v21 is now supported

Thu, 20 Nov 2025 00:00:00 GMT

Angular v21 was released today and it is supported on Netlify on day one. To upgrade, follow the Angular upgrade steps and update @netlify/angular-runtime to v3.0.1 or later. Learn more:

Angular v21 Release
Angular on Netlify
Angular Runtime

React Router 7 apps can now be deployed to Edge Functions

Mon, 10 Nov 2025 15:56:31 GMT

React Router 7 apps on Netlify are deployed to Serverless Functions by default. Now, you can choose to deploy your app to Edge Functions instead, bringing your page renders, data loaders, and actions closer to your users while lowering cold start times. How to use it

Ensure you're on version 7.9.0 or later of React Router:

npm install react-router@latest @react-router/node@latest @react-router/dev@latest

Update to the latest version of the Netlify React Router plugin:

npm install @netlify/vite-plugin-react-router@latest

Enable the new edge option in your vite.config.ts (or .js):

export default defineConfig({ plugins: [ reactRouter(), netlifyReactRouter({ edge: true }), // <- deploy to Edge Functions netlify(), ], })

Finally, create a file at app/entry.server.tsx (or .jsx) containing this single line:

export { default } from 'virtual:netlify-server-entry' On your next deploy, page renders, loaders, and actions will all run in an edge function. When to use it Choose Edge Functions when:

You need minimal latency for your globally distributed users (edge functions run on the node closest to the user)
You need to optimize cold starts (initialization is faster with the slim Deno edge runtime)
Your data loaders and actions make requests to databases and APIs that are also globally distributed, or none at all
You need to support very large request or response bodies (Serverless Functions have a 6 MB limit)

Choose Serverless Functions when:

Your data loaders and actions make requests to databases or APIs that are centrally located (canceling out much of the benefit of edge compute)
Your server-side code is CPU-intensive (Serverless Functions run on more powerful machines)
You need longer execution times (Functions allow up to 30s clock time, while Edge Functions are limited to 50ms CPU time)
You cannot use Edge Functions due to their runtime constraints or limitations

Next steps

Create a new React Router 7 project with our template
Read the Netlify React Router plugin docs for more details on deploying to the edge

React Router 7 middleware now supported

Fri, 24 Oct 2025 15:29:00 GMT

React Router 7 recently launched its long-awaited middleware feature, stable since v7.9.0. Middleware is now fully supported on Netlify. How to use it Ensure you're on version 7.9.0 or later of React Router: npm install react-router@latest @react-router/node@latest @react-router/dev@latest Upgrade to version 2 of the Netlify React Router plugin: npm install @netlify/vite-plugin-react-router@latest After that, middleware works out of the box. Next steps

Check out the full React Router middleware docs
Create a new React Router 7 project with our updated template
Read the Netlify React Router plugin docs for more on loader/action context and to access type-safe Netlify context in middleware

Next.js 16 is ready to deploy on Netlify

Tue, 21 Oct 2025 23:59:00 GMT

The Next.js 16 release is here and Netlify is ready. Deploy the latest version, including Turbopack, React Compiler, and enhanced caching APIs, with zero configuration.

Turbopack (stable): Up to 10× faster Fast Refresh and 2-5× faster builds
React Compiler (stable): Automatic memoization for smoother re-renders
Improved caching APIs: revalidateTag with cacheLife profile argument for Stale-While-Revalidate behavior and Server Actions-only updateTag to immediately refresh cached data

Template update We’ve updated the Next Platform Starter to v16, showcasing Turbopack and the new caching APIs in action. In our tests, the project saw a 2.8× faster next build with Turbopack. Upgrading to v16 on Netlify If you’re upgrading from v15, no Netlify configuration changes are required. Teams that have opted out of automatic updates for Netlify’s OpenNext adapter will need to manually upgrade, or simply opt back in to receive automatic updates. Resources

Deploy the demo
Read the Next.js 16 release
View Next.js on Netlify docs

Angular 20 support

Wed, 28 May 2025 19:49:47 GMT

Angular 20 is now fully supported on Netlify with zero configuration required. What's new

Full Angular 20 compatibility: Deploy Angular 20 projects with all the latest features including stable signals APIs, zoneless change detection in developer preview, and incremental hydration.
Updated Angular template: We've refreshed our Angular starter template to showcase Angular 20's capabilities, including the new control flow syntax and simplified component naming conventions.
Optimized SSR support: Angular 20's stable incremental hydration and route-level rendering modes work with Netlify's edge network for faster, more efficient server-side rendering.

How to get started Add your existing Angular 20 project by connecting your Git repository–or deploy our template–no configuration changes needed. For new projects, try our updated template with Angular 20's latest features. If you're planning to upgrade from version 18 or earlier, check out our guidance on the Angular runtime.