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.
NuxtLabs is joining Vercel
31–40 of 83 posts
Re: NuxtLabs is joining Vercel
#32Earlier quoted context omitted.
> 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. https://uvr.esm.is/ https://pinia-colada.esm.dev/
There is no universe in which Astro is a better choice than Nuxt for Vue-based MPA, SSG or SPA with SSR situations.
No universe, huh?
Re: NuxtLabs is joining Vercel
#33Pretty 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.
Here's to holding out hope Tanstack stays independent
Re: NuxtLabs is joining Vercel
#34This is awful news unless hopefully this REALLY doesn't influcence the development into a more react-y way away from Vue.
Or having the framework adopt design patterns optimized for Vercel infra, like Next is (and why I replaced it with Tanstack)
Re: NuxtLabs is joining Vercel
#35"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.
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.
Re: NuxtLabs is joining Vercel
#36Pretty 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.
Embrace, extend, extinguish… Tale as old as… well, the 60’s… but still, it’s an old tale.
I've been trying to get embraced, extended, and extinguished for years.
Re: NuxtLabs is joining Vercel
#37Earlier quoted context omitted.
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-b…
It's only "more capable" in the sense that yes, ultimately, it's JavaScript and you can do a lot with JavaScript. But Astro's model is "generate markup once, serve statically". Nuxt's model is "Server-Side JavaScript"
From a cursory reading of Astro's docs their model/philosophy seems to be more like "fast by default."
So their philosophy is to start with zero client-side javascript, even when one is using components from javascript-heavy frameworks like React or Vue. Interactivity is apparently something one has to explicitly opt-in to by adding a client:* directive, rather than it being the default.
The migration guide states, "Astro projects can also be SSG or SSR with page level prerendering," which puts it on par with Nuxt in that regard.
A difference I've noticed regarding server-side features is that Astro allows one to "define and call backend functions with type-safety."[0] which even Nuxt doesnt offer in such a convenient and type-safe manner. I'm pretty happy with what i'm seeing in Astro's docs so far.
Re: NuxtLabs is joining Vercel
#38I'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!
Re: NuxtLabs is joining Vercel
#39Earlier quoted context omitted.
> 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
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?
> 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.
Re: NuxtLabs is joining Vercel
#40Earlier quoted context omitted.
Astro is nice, but its a different model than Nuxt, more suited to static sites.
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-b…
Even if you use the Astro view transitions API to make a SPA, its client side router falls short of other frameworks that are more truly SPA oriented.