Paid for it not even a month ago, kind of a bummer 😅

@Buzut you can always contact them for a refund, might not be too late.

yeah, I'll shoot em an email tomorrow, after I finally find the time to finish what I told Daniel I'd do 3 weeks ago 😬

So...if NextJS prefers to use trailing comas as a convention and Nuxt too, then it's Vercel's evil hand hovering over it?
Definitely not just a healthy convention, right?

Having some unified common ground across frameworks just makes sense.
Not reinventing the wheel but keeping some kind of consistency in Solid, Svelte, Vue, React approach etc...is kinda healthy and unrelated to any illuminati evil scheme tbh.
But maybe you (@hoachnt) like to just learn things again when using a new tool every morning.
Most people are fine with universal conventions, especially in this damn JS ecosystem that is wild-west most of the time.

@kissu
Alright, fair enough — I might be exaggerating a bit. In the end, it's all about personal preference.
But when Nuxt turns into just a wrapper like Next, without offering its own distinct features or implementations — just doing it all the "Vue way" — then I start asking myself: why do I even need it?
If I can just use React + Next, especially now that React is clearly moving toward the same developer experience as Svelte and Vue, what's the point?
Maybe the only real advantage Nuxt still has is its cozy and well-integrated ecosystem — but even then, React and Next have like 300 billion tools, plugins, and solutions for literally everything.
We'll see — time will tell. For now, I'm actually thinking of trying out Astro + Vue.

@hoachnt The point is the community you feel more comfortable with. I really hope it ends up being a broader one, the web community; it was way too fragmented by frameworks until now.

@hoachnt honestly, at some point you're realize that some of those personal preference things do not even matter most of the time and you'll become more pragmatic regarding the goal you're trying to achieve rather than the fancy syntax or cool API tied that specific framework.
Are you ready to trade: [few extra keystrokes + stable for 5 years] over [cool fancy API but breaking change in 6 months]? 😬

Most people are anyway using Next or Nuxt for the wrong reasons and got baited too easily.
It's mostly comfort and ease of use because of habits over the years.
Honestly, you writing React, Vue, Svelte or whatever doesn't really matter at the end of the day and is just making you more bitter cuz you want to stay in your club and fight anybody saying mean things about it.

I never loved the over-engineered approach that React imposed and all of it's intricate ever-changing APIs.
Vue also got quite some steeper and more cumbersome bumps in the past years.

You could give a try to Astro + Vue indeed.
Maybe also try other alternatives like Deno, Fresh, etc.
You can also try something totally different, frontend is quite a vast topic.
Lots of people complain about React, Vue blah blah...while it does not matter. Stop wasting your precious time.
Just try something new. 💖
Maybe even some backend might be fun, or 3D, or music-creation, or whatever you see fitting your coding curiosity.

You can also try new hobbies in life too with idk: bouldering, DIY 3D printing, robotics, lock-picking, inline skating.
Touching grass out of all of this nonsense gonna just make you more happy on a daily basis honestly (unlike me yapping in this gloomy reply 😂).

And if you REALLY feel adventurous, then you can always connect to other communities like my dear @alvarosabu ❤️‍🩹 is suggesting above. But keep in mind that frameworks are just tools, led by communities/folks and that they will be ever changing, full of politics and can sometimes also not be as nice as you expect them to be.

@kissu I couldn't agree more, especially regarding your thoughts on living and experiencing life outside of the screen.

This collaboration between Vercel and NuxtLab is great news.

That said, I can understand some of the scepticism and trepidation voiced here in the comments intimating that corporate takeover and subversion could be insidiously happening to this much loved frontend framework but here's my take on it.

As an ongoing dabbler and hobbyist coder I fully rely on open source for my personal endeavours, its mind blowing that I have access to professional and enterprise grade frameworks, tooling etc that enables that personal journey. If I had to pay a hefty subscription I couldn't use these amazing products as my use case couldn't justify such expense.

There's the rub right there, these amazing projects are produced by amazing communities, like this one, being facilitated by brilliant engineers especially those in the core team and they've got bills to pay, sponsorship is great but what Vercel offers is even better.

I think collaborations between corporate sponsors like Vercel provide such a needed function in making the financial model work for everyone, perhaps especially those amazing engineers in the core team. For sure there are risks of competing interests and misaligned agendas but the core teams for these open source projects have been massively invested in their vision, efforts and activities with their involvement over years, to such an extent that it would be extremely surprising to find these guys throwing it all to the wind.

Objectively considering what has been presented so far I just can't see the downside, the collaboration has already brought massive benefits to the community and wider user base, consider this quote from one of NuxtLab's co-founders;

"* Release Nuxt UI v4 with all Nuxt UI Pro components available for free to everyone, as well as our Figma Kit.

• Open source a self-hostable version of Nuxt Studio, designed to integrate directly with your Nuxt Content site as an admin to edit your website.
• Make NuxtHub agnostic to support other providers, integrating with Vercel’s Marketplace offerings like Postgres and Redis will become seamless.

Looking ahead, AI will be a new area of focus for us. We’re exploring how to bring AI into the Nuxt developer experience. Helping you ship ideas faster. We’re also working closely with Vercel’s AI teams, including v0, and continuing to experiment with local tooling like MCP.

Sébastien Chopin"

Wow, more open freely accessible stuff for the community that enhances the DX, provides quicker routes to market for the products you develop, more community stability with the promise of more tools and an even more productive DX, what's not to like.

If you do see it going south and you don't like the direction the community is taking, its open source, if you have the skills and ability, fork it.

On the other hand, if you are like me, an end user with limited ability, talent and time, just say thanks NuxtLab community and good luck on your new collaboration.

and refunds for all purchasers/investors :-)

urchasers/investors :-)

I wouldn't bet on it 🤣

Drats my NuxtUI pro based websites aren't going to look so unique anymore! lol.
I'm going to need to start customising my designs a bit more. haha

nuxt is staying as an independent project - nothing is moving out of nuxt/ to anywhere else

Thanks for the clarification Daniel! Once again, congrats and I hope they have some bouldering perks for you all ;)

You put the "u" in Nuxt .... keep it there 😉

Wish you all the best

@harlan-zw a question off-topic please ! Any chance for Paddle or Polar in the Nuxt scripts Registry ? Sorry to ask here

@Deeyuude probably you can get better response with an issue / PR on the dedicated repo 🙂

because it's too coupled with tailwindcss !

Try my UnoCSS preset for integrating UnoCSS with Nuxt UI: https://github.com/lehuuphuc/unocss-preset-nuxt-ui

Sure, but for how long?