The new @netlify/nuxt module brings the complete Netlify platform directly into your nuxt dev server: Functions, Edge Functions, Blobs, Image CDN, headers, redirects, environment variables… it all just works. This lets you (and agents) stay in the zone on your machine, without workarounds or additional tools.
#How this helps you
Following our Vite plugin announcement, we’re bringing the same seamless experience to Nuxt developers. But here’s where it gets interesting: this isn’t just about your local development convenience. It will also enable AI code agents to build fully-functional Netlify apps without needing to know about Netlify CLI or any other unique aspects of how you deploy your app to the web.
We’ve personally seen agents go off on a wild goose chase: “Hmm, it looks like the Blobs environment is not configured. Let me try another approach. I’ll temporarily replace the Blobs usage with a mock implementatio—” Ctrl-C Ctrl-C Ctrl-C. @netlify/nuxt fixes all that.
#Getting started with @netlify/nuxt
Add the @netlify/nuxt module to your Nuxt 3 or 4 app:
npx nuxi module add @netlify/nuxtThat’s it.
This is supposed to be a guide, but there’s only one step, so, uhh, we’ll tell you more about what this gets you and what to try next.
#What you get out of the box with @netlify/nuxt
#Netlify Functions
Drop a function in netlify/functions/hello.ts and it’s immediately available at /.netlify/functions/hello or your configured path. It just works in nuxt dev.
#Edge Functions
Same story for Edge Functions in netlify/edge-functions/. Full Deno runtime, geolocation, all the edge goodies running locally.
#Blobs
Need persistent storage? Netlify Blobs works locally with zero setup.
#Image CDN
Image transformations work locally exactly as they will in production. Resize, format conversion, quality optimization… no meme generation yet, sorry.
#Headers & Redirects
Your _headers and _redirects files and equivalent config in netlify.toml are parsed and applied in real time. No need to guess if that redirect rule will actually work.
#Environment variables
There are so many ways to configure environment variables on your Netlify project: on your team, on your project, in your netlify.toml scoped to a deploy context, in the UI scoped to just functions… They all just work in nuxt dev.
#How to power up your AI coding workflow
Here’s what’s game-changing: when you combine @netlify/nuxt with tools like Netlify MCP, AI code agents get a complete feedback loop. They can, say:
- Write an Edge Function
- Test it immediately in your dev server
- Debug based on real responses (psst: some can use Playwright to browse interactively)
- Iterate until it’s perfect
No deployment steps. No context switching. No “let me explain that you need to install and use Netlify CLI for Netlify Functions to work” conversations with your AI agent.
#Real-world example of using @netlify/nuxt
We’ve built a complete live Q&A application that demonstrates these capabilities in action. It was almost entirely written by Claude using Netlify MCP + @netlify/nuxt. The agent had full access to test Edge Functions, store data in Blobs, and iterate on the entire application—all without deploying or installing netlify dev.
Check out the demo: https://queue-and-eh.netlify.app/
This isn’t a toy example—it’s a production-ready application that can replace an actual SaaS solution Netlify was paying for to use in company-wide meetings. It implements real-time updates using Server-Sent Events (SSE) via Netlify Edge Functions and persistent storage with Netlify Blobs.
To see @netlify/nuxt in action, click the Deploy to Netlify button above, run npx netlify@latest clone <your created repo url>, follow the instructions, and run nuxt dev. Try adding an AI-generated cover image when a new event is created, optimized on the fly with Netlify Image CDN!
#👀 What’s next?
With the Vite Environment API in the works, the recently launched Netlify Vite plugin, and the Nitro team’s future vision for Nitro to become a Vite plugin and add environment-specific dev mode capabilities, there’s a a lot of exciting work on the horizon in the ecosystem.
You can expect to see even more seamless integration between Nuxt, Vite, and Netlify in the future.