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.

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.

"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.

As someone that's been saying Vercel should be avoided for years now, it's nice to finally start seeing more hesitation from others.

They now, to varying degrees, directly employ core maintainers for Svelte, SvelteKit, React, Next, and now Nuxt. This is a very clear systematic overtaking of the web ecosystem. They're a private business, so these moves must be in the interest of increasing profits. It's not just out of the goodness of their hearts.

It's somewhat unfortunate that technical and business-savvy people would both, in my experience, disregard a study saying tobacco is good if it's funded by RJR, and be excited about a giant tech company employing core maintainers for the majority of new web-related software projects. Yes, they're open source projects that you can fork. But if Vercel has influence in the direction of these projects (and of course they do) it should give people much more hesitation to use them than it seems to.

At this point, using any of the technologies that Vercel has its hands in tells me that whatever uses it - a business, project, whatever - doesn't plan to function in five years.

Some more details by Daniel Roe: https://github.com/nuxt/nuxt/discussions/32559

As also seen here: https://news.ycombinator.com/item?id=44500544

This is like Autodesk having 3D Studio Max, buying up Maya and Softimage, leaving Houdini as the only independent 3d package.

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!

A lot of comments express concern about their favorite framework losing independency. I always worry about Angular being made independent. lol

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.

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.

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.

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.

The announcement on Vercel's side: https://vercel.com/blog/nuxtlabs-joins-vercel

This is awful news unless hopefully this REALLY doesn't influcence the development into a more react-y way away from Vue.

That's a shame.

So now Nuxt joins Next in the never to use pile.