On 8 July Vercel announced that it is acquiring NuxtLabs. NuxtLabs is the company founded in 2017 by the original authors of Nuxt, and it has funded and employed many of the people who build Nuxt and Nitro. It published its own announcement the same day, and the Nuxt team lead opened a discussion on GitHub titled The future of Nuxt.
If you are learning Nuxt, the short answer is that nothing in your code or your deployment changes. Two things might touch you: Nuxt UI Pro is to become free, and sponsorship money is moving to Open Collective. Everything this post says about the deal comes from those three texts, and it does not guess at what they leave out.
What was announced
Vercel's post, written by its chief executive, calls NuxtLabs the "creators and stewards of Nitro and Nuxt" and says the company and its open source team are joining Vercel. For scale, it says Nuxt is downloaded more than a million times a week. It presents Nitro, the server layer underneath Nuxt, as a portable standard that serves other frameworks and platforms too.
NuxtLabs' post explains the motive from its side. The company no longer has to split its attention between maintaining Nuxt and funding that maintenance; the people who build the framework get paid to build the framework.
The GitHub discussion adds the staffing detail. Four members of the core team become Vercel employees working full-time on open source, and the rest of the team stay freelance or employed elsewhere. The current lead continues to direct Nuxt's technical and strategic work.
What the announcements say stays the same
The commitments are specific enough to hold someone to, but the three texts do not all make the same ones:
- Nuxt and Nitro remain independent open source projects under the MIT licence. Vercel's post makes both promises; NuxtLabs' post repeats the licence and the discussion the independence.
- The roadmap stays public (all three texts) and governance stays open (Vercel's post and the discussion). In reply to a question, the discussion's author adds that nothing moves out of the
nuxt/GitHub organisation. - Nitro keeps serving every framework and every hosting vendor "without lock-in", in Vercel's words.
- Work on Nuxt and Nitro continues "with the same focus and care", in NuxtLabs' words.
The discussion also says that choice is at the heart of Nuxt: choice of modules, databases, bundlers, routers and deployment platforms. None of the three texts announces a change to a Nuxt API, a module, a default or a release date.
What changes: sponsorship, paid products and AI plans
Three things change, and none of them is the framework itself.
Sponsorship moves to Open Collective, a funding platform where a project's budget and transactions are public. NuxtLabs says all sponsorship funding will be moved there, for transparency and so that it goes directly to Nuxt core and community contributors. The GitHub discussion notes that community sponsorship can now support more contributors.
NuxtLabs' paid products are to become free. Vercel's post says that over the next few months Nuxt Studio MDC, Nuxt UI Pro and NuxtHub Admin will become free and open source. NuxtLabs' post gives the plan product by product:
- Nuxt UI Pro: the next major version of Nuxt UI will ship with every UI Pro component free for everyone, plus the Figma kit.
- Nuxt Studio, the editor for Nuxt Content sites: a self-hostable open source version.
- NuxtHub, NuxtLabs' platform for deploying Nuxt apps on Cloudflare: support for other providers, with Vercel Marketplace services such as Postgres and Redis integrated.
For a learner, the first of those is the practical one: a component library that used to cost money will not.
NuxtLabs also says it will explore bringing AI into the Nuxt developer experience, working with Vercel's AI teams and experimenting with local tooling. That is stated as an area of exploration, not a feature, so there is nothing to install or evaluate yet.
Nothing changes in your project
Your nuxt.config.ts is the same file it was on 7 July, and so is every command you run. The framework's licence is a field in its package.json, and you can read it from the npm registry yourself:
npm view nuxt license
That prints MIT today and the announcements say it will keep doing so.
Deployment still goes through a Nitro preset, the setting that tells Nitro which host to build for. A project that deploys to Cloudflare, Netlify, a Node server in a container or a static host keeps doing exactly that, with the same configuration. If you chose a preset yourself, it is one line in nuxt.config.ts:
export default defineNuxtConfig({
nitro: {
preset: 'cloudflare-pages',
},
})
Nitro detects several hosts on its own (Cloudflare, Netlify and Vercel among them), so many projects do not even have that line. Nothing in the announcements asks you to add one, change one, or move to Vercel. Modules such as @nuxt/content, @pinia/nuxt, @nuxtjs/i18n and @nuxt/image are separate packages, and none of the texts mentions a change to any of them.
What a learner should do
Nothing different, with two small exceptions.
First, if you were about to pay for Nuxt UI Pro, wait: its components are to be free in the next major version of Nuxt UI. NuxtLabs plans that release for the coming months and gives no date.
Second, if you sponsor Nuxt, the money will go through Open Collective. None of the texts says whether current sponsors need to do anything, so wait for instructions from the Nuxt team before you change a payment.