NuxtLabs is joining Vercel
44 comments
·July 8, 2025joshdavham
9dev
That’s awful. Vercel has pretty much a monopoly on the hybrid framework space now, and it’s going to ruin everything. NEVER did a monopoly do any good to anyone but its holder.
Props to Vercel, I guess. Enjoy your champagne. Increased the share holder value, job well done! Clap, clap.
softfalcon
Embrace, extend, extinguish…
Tale as old as… well, the 60’s… but still, it’s an old tale.
MarcelOlsz
I've been trying to get embraced, extended, and extinguished for years.
verdverm
Here's to holding out hope Tanstack stays independent
ayhanfuat
"Vue is currently the only mainstream framework that remains independent. (i.e. not dominantly owned / backed by a single corporation" Evan You https://x.com/jpschroeder/status/1762764818254016513/photo/1
I know Nuxt is not Vue itself, and I'm not saying Vue is no longer independent — but I do think it's worth remembering that independence is something highly valued in the Vue community.
franky47
Wouldn’t Void 0 contradict that statement? It’s more oriented towards lower-level infrastructure though (Vite, Oxc and other tooling), but it extending to support Vue wouldn’t be a surprising move if it became necessary.
danielroe
Nuxt maintainer here.
there's lots to say here, but from my point of view, Vercel's backing Nuxt largely _because_ of our open vision.
our open approach isn't an optional extra. it's a core value we all share on the team - and indeed, I think, is as close to a core value of the web as I know.
we've pioneered cross-framework adapters and the provider pattern in all we build and there is no way we are changing direction or vision.
nuxt remains an independent framework, like svelte. the fact that a number of us on the team are employed to work full time on OSS is _great_ news for OSS sustainability.
toddmorey
I hope so! The Nuxt adapters and provider pattern are amazing! Its truly impressive how well done it all is and how portable Nuxt is and how other projects have been able to use a lot of the same OSS tech you've created to get portability from the jump.
The portability story for Vercel's own Nextjs is a disaster.
eclipxe
Huge fan of Nuxt and your work, excited for this!
esher
Some more details by Daniel Roe: https://github.com/nuxt/nuxt/discussions/32559
As also seen here: https://news.ycombinator.com/item?id=44500544
mirzap
Vercel’s announcement: https://news.ycombinator.com/item?id=44499838
meekaaku
This is like Autodesk having 3D Studio Max, buying up Maya and Softimage, leaving Houdini as the only independent 3d package.
BOOKHOUSEUK
blender.org has entered the chat.
Cu3PO42
I'll admit that I'm skeptical and that I'd generally prefer less centralization. I love what Nuxt has done with Nitro, for example, and it being compatible with "all" hosting providers. Compare that to Next, which is "best on Vercel". Also see TurboPack, which seems to be effectively exclusive to Next.
That said, I can only imagine how incredibly freeing it must be to not have to worry about funding, so I couldn't blame them in the slightest. I really with them the best and hope Nuxt continues to be great. Looking forward to v4 soon!
MortyWaves
Nuxt has always been a strange tool that doesn’t really fit well into any good use case, unless your only experience is Vue and Nuxt.
Hard to see the real reason for Vercel to do this. The pessimist in me wonders if perhaps they are hoping to influence how Vue is developed in the same way they now influence how React is developed after hiring several React team members.
But even that doesn’t seem that likely considering the relatively tiny Vue market share and microscopic still Nuxt market share.
I also consider its “community” to be a strange place too. It’s on Discord, and a couple of years ago common internet abbreviations were considered ban worthy rule-breaking offences.
Even the word “lmao” would get you an instant warning from a bot. The framework itself and its oddball community were enough poor experiences for me to stop using it pretty quickly.
pier25
> doesn’t really fit well into any good use case
I agree.
If you want an SPA just use Vue's official router. It's getting better now thanks to Eduardo working on file-based router, data loaders, Pinia colada, etc.
If you want a static site or MPA, Astro really seems like a better choice than Nuxt.
threetonesun
Get Nuxt people paying to deploy on Vercel and over time force the user base to Next and React would be my guess.
_bent
It's an aquihire
eclipxe
I actually love Nuxt. If you want all the fullstackness of Next, but without having to deal with React, it's perfect.
yieldcrv
> Hard to see the real reason for Vercel to do this.
Next supremacy is very obvious
Kills all those Linkedin threads about moving away from Next. Kills the indecision for what employment-seeking devs need to optimize for. Makes those job descriptions less all over the place and even more Next focused
eclipxe
That doesn't make any sense at all. Vercel wins either way if you choose Next, Nuxt, or Svelte. Seems obvious - why would they care if you use Next vs. Nuxt now?
bakugo
> Vercel wins either way if you choose Next, Nuxt, or Svelte. Seems obvious - why would they care if you use Next vs. Nuxt now?
Because maintaining three projects is more expensive than maintaining one. It's within their best interests to quietly extinguish any alternatives in favor of the one that most closely matches their vision.
etchalon
What?
Nuxt is the only "out-of-box-everything-works" framework for Vue.
So yes, if you use Vue, you use Nuxt.
strickjb9
I'm baffled by the doom-and-gloom reactions here. Nuxt remains what it's always been: the best convention-over-configuration framework in existence. It's built on Vue which is opinionated as hell, and you get all the benefits of that. The "vendor lock-in" concerns are frankly overblown. At the end of the day Nuxt produces artifacts you can deploy anywhere - AWS, Cloudflare, your own infrastructure, or yes, Vercel. The alternatives (underfunded OSS maintainers burning out) are way worse than having a well-funded team with aligned incentives. If anything this validates that Nuxt is valuable enough for a major platform company to invest in. I'll take that over watching great tools die from lack of resources.
9dev
Everything you say is now subject to change due to strategic decisions by a single entity that owns almost all horses in the race. The things you take for granted now can disappear tomorrow, no matter how many times they pinky promise not to.
Nuxt is great, but Chromium is great too. Yet, Google has become the driving force behind changes to the web platform, for better or worse. That’s not a desirable situation, and certainly not the only one: it’s not like there’s only a single company out there able to fund open source software. I desperately hope we, collectively, will figure out a better financing model in the future.
AbraKdabra
This is awful news unless hopefully this REALLY doesn't influcence the development into a more react-y way away from Vue.
verdverm
Or having the framework adopt design patterns optimized for Vercel infra, like Next is (and why I replaced it with Tanstack)
eclipxe
Why would it? That doesn't really make sense?
aosaigh
Honestly, this is terrible news. A number of the core team of Nuxt.js are joining Vercel and NuxtLabs itself is acquired by Vercel.
I choose Nuxt.js and Nuxt UI Pro specifically because they aren't Vercel products. I built two SAAS MVPs over the last year based on this, now I'll have to wait and see what Vercel (their competitor) wants to do with it.
kelthuzad
You've expressed my thoughts to a tee. I will start exploring Astro and see what the migration process is like. Many devs questioned my usage of Nuxt over Astro to begin with, so this is a good opportunity to learn.
jt_b
Astro is nice, but its a different model than Nuxt, more suited to static sites.
kelthuzad
I'm just reading the docs and it seems more capable than that: https://docs.astro.build/en/concepts/islands/#server-islands
I have also just discovered a dedicated section for the migration from Nuxt to Astro:
>Key Similarities between Nuxt and Astro
Nuxt and Astro share some similarities that will help you migrate your project:
- Astro projects can also be SSG or SSR with page level prerendering.
- Astro uses file-based routing, and allows specially named pages to create dynamic routes.
- Astro is component-based, and your markup structure will be similar before and after your migration.
- Astro has an official integration for using Vue components.
- Astro has support for installing NPM packages, including Vue libraries. You may be able to keep some or all of your existing Vue components and dependencies.
https://docs.astro.build/en/guides/migrate-to-astro/from-nux...
null
impulser_
Vercel isn't a competitor to Nuxt. Vercel benefits from allowing any frontend framework to be deployed on their service.
All you have to look at is Svelte, which Vercel hired all the developer of, and that turned out to be a great thing. Svelte and SvelteKit are better than ever and nothing they have done since has shown to be forced by Vercel.
codybontecou
Vercel benefits from moving as much of the logic to the server (their paid services) as possible.
etchalon
Vercel benefits from not letting other, better, cheaper architectures like Cloudflare Workers get better treatment than them from popular framework authors.
blinky88
The announcement on Vercel's side: https://vercel.com/blog/nuxtlabs-joins-vercel
etchalon
Ugh. Can they not? Who do I talk about them not?
NuxtLabs was doing great work building out support for Cloudflare, making it a viable alternative to Vercel.
Now, I'm sure all that work will get dropped and we'll be stuck with only Vercel being a first-class host for Nuxt-based applications.
Pretty incredible that now Next.js, Svelte/kit and Nuxt will be under Vercel.
This could be a great thing as now all of these devs are much better supported in their work, but I’d be lying if I didn’t say that this situation makes me quite nervous.