Changelog
-
Today we’re announcing two major updates for Nuxt developers on Netlify:
Day-One Nuxt 4 Support
Nuxt 4 launched today, and Netlify is ready. Deploy your Nuxt 4 apps with zero configuration changes—everything just works. Everything is fully compatible from day one.
Learn more about leveraging platform primitives with Nuxt.
Full Platform Emulation in Your Dev Server with @netlify/nuxt
We’re also launching
@netlify/nuxt
today, a new Nuxt module that brings the entire Netlify platform into your local development environment. Functions, Edge Functions, Blobs, Image CDN, env vars, headers, and redirects all work directly innuxt dev
—no separate CLI required.Add the module to your Nuxt 3 or Nuxt 4 app with one command:
npx nuxi module add @netlify/nuxt
This simplifies local development and enables AI coding assistants to build full-stack apps with immediate feedback.
-
Netlify’s smart secret scanning automatically detects API keys, tokens, and credentials in code. Pro plan feature blocks deployments with potential secrets to keep your applications secure.
-
Netlify DB provides serverless PostgreSQL that provisions automatically with one command. Built for AI agents and modern development workflows. Start building fullstack apps faster with zero configuration required.
-
You can now install the Netlify MCP on Cursor with a single click.
Check out our docs on the Netlify MCP server here.
-
The Netlify MCP Server enables AI agents to deploy applications directly from your editor. Built on the Model Context Protocol, agents can now complete the full development cycle from code to production.
-
Netlify is now the official deployment partner for Vite, plus introducing our new Vite plugin. Access the Netlify platform directly into your local dev environment.
-
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.
-
-
Netlify CLI 21.4.1 has a cleaner look, simplified workflows, and a new command.
Install the latest version:
npm install netlify-cli -g # or yarn global add netlify-cli
Onboard to Netlify projects with
netlify clone
commandPull an existing Netlify project locally from its repo with one command:
netlify clone <repository-url>
Clones the repo and links it to the right Netlify site–ideal for onboarding or switching projects.
Builds are included with
netlify deploy
The deploy command now runs a build step by default, eliminating separate build commands.
Instead of
netlify build && netlify deploy
ornetlify deploy --build
, simply run:netlify deploy
To deploy without building, use netlify
deploy --no-build
.Smarter manual setup
netlify init
now auto-detects your framework and suggests the right build settings. It’ll even help you create a netlify.toml if you don’t have one.Better updates and onboarding
Additional improvements include:
- Better update notifications with links to release notes
- Improved onboarding guidance with clearer next steps and resource links
- Reorganized help command with better documentation references
-
The Next.js team recently disclosed CVE-2025-32421, a low-severity vulnerability allowing for CDN cache poisoning in some scenarios.
The engineering team at Netlify has confirmed that all Next.js sites on Netlify are not vulnerable. The vulnerability requires use of a CDN that may cache responses without explicit Cache-Control headers, but Netlify’s CDN never does so.
As a general security precaution, we recommend upgrading to the latest versions of the Next.js framework and allowing automatic updates of the OpenNext Netlify Next.js adapter.