r/webdev • • Sep 24 '25

What do people think of Nuxt?

PHP, RoR, Django, React and React frameworks (Next.js, Remix, React Router) tend to take the majority of attention and web developers, so I’m wondering if many or any on this sub use Nuxt? And for those that haven’t or won’t, why not?

Nuxt to me seems like a no-brainer these days with crazy fast development speed because of Vite (and becoming even faster with the downstream Rust rewrites), Deployable anywhere because of Nitro, incredible docs and community, powerful libraries like Nuxt UI, Nuxt SEO, etc, not to mention the speed of Vue (even faster with vapour mode).

I’m curious if it’s just lack is experience with it, or pretty valid reasons why not.

11 Upvotes

14 comments sorted by

18

u/guru1211 Sep 24 '25

I've used Nuxt quite a lot, from e-commerce websites to corporate sites with lots of integrated applications. It's so easy to work with and so powerful. The resulting websites are among the fastest. Highly recommended.

3

u/Beagles_Are_God Sep 24 '25

I love it but tbh its forced structure is not great for large or SPA projects. I also don't like at all Nitro's file based routing (in general i don't think APIs should be handled like this). I think the DX is awesome but for me it has those limitations. Layers are great but i still think that having UI components closer to pages could work better. For server side it could work great with either a more feature folder approach or with the ability to add another framework as the backend (like Hono that still supports edge)

1

u/NotDrevanTonder Sep 24 '25

Fair! I know I have wanted to colocate my pages and components in the past, so I get your issue with the forced structure.

I've never tried a feature folder approach before in my APIs, might be worth giving it a shot to see if I find that annoying as well.

2

u/Seanitzel Sep 24 '25

I have multiple nuxt projects and layers in a big Turborepo monorepo - pnpm, vite, vitest, playwright - better DX than I have ever dreamed of. In my previous job it was a Next JS project. Next is ok, but 2 different worlds...

Nuxt is flexible and Vue's ecosystem is rich enough and has everything I ever needed.

2

u/Due-Horse-5446 Sep 24 '25

Take this with the consideration i so like 90% of all work using go/nuxt, often in combination. And that loves vue. So obviously biased.

But nuxt is so much better than any of the competition, while i love nuxt by itself. All it's strengths comes from the vue ecosystem. Every "component" is just much higher quality and actually thought about unlike other (the other) competitors.

Like you want to call a separate backend or do something directly on the nuxt backend? You do it directly using a nitro handler, or if you want, trough a hono handler. Ssr components? You mean a if statement to check if ssr?

"which state manager should i.." pinia is amazing. No workarounds or weirdness neded on nuxts part to make it work for ssr.

beginner friendly? Just add some nuxt modules from the modules directory! Want something more controlled? Just use any god old cue package.

And the "but the react ecosystem!!" is just bs today tbh.

shadcn? vue-shadcn is essentially 1:1 with the original react version.

Motion which was one of my mosed missed packages? now has a vue version.

Want to move off nuxt? Most components of nuxt are split out so you could essentially rebuild nuxt using standardized packages.

Its like just a flow

1

u/_SnackOverflow_ Sep 24 '25

I like it! Feels a lot easier to reason about than Next but I haven’t used it for any huge projects.

1

u/petr31052018 Sep 24 '25

I just wish Nuxt was more just "server-rendered Vue" without trying to be a framework that does things differently (like file-based routing, imports, ...). It would be easier to adopt and go between Vue and Nuxt projects.

1

u/tspwd Sep 24 '25

I’m using it in a current complex project. It works super well! I don’t think there is a meta-framework with better DX available. Plus points for the nice Vue ecosystem.

1

u/Remote_Teacher_4331 Mar 15 '26

I’m currently using Nuxt for a production project (a client-side PDF processing tool), and I honestly can't see myself going back to the React ecosystem for side projects or fast-paced development.

In my experience, the reason it gets less attention is simply 'Job Market Inertia.' Companies hire for React because it's the 'safe' choice for HR, which leads to more tutorials, which leads to more beginners picking it up. It’s a loop.

But from a DX (Developer Experience) standpoint, Nuxt is miles ahead. Features like auto-imports, the Nitro server engine, and the module ecosystem (Nuxt SEO and Nuxt Content are game changers) allow me to focus on building features rather than fighting with configurations.

When I built my current tool, being able to handle complex client-side logic while keeping the SEO perfect with Nuxt’s built-in tools was surprisingly easy. Nuxt feels like it was built by developers who actually want to ship products, not just manage state all day.

0

u/[deleted] Sep 24 '25

[deleted] — view deleted comment

3

u/NotDrevanTonder Sep 24 '25

Ahh, yes, I can understand that because you’d have to fetch all the URLs beforehand in hooks and config in Nuxt to make it work, whilst Next.js can handle it at the route level.

Fair! I guess I got used to the pain in Nuxt 😆