Next.js vs Nuxt: What are the differences?
Next.js and Nuxt are primarily classified as "Frameworks (Full Stack)" and "Front-End Frameworks" tools respectively.
Some of the features offered by Next.js are:
- Zero setup. Use the filesystem as an API
- Automatic server rendering and code splitting
On the other hand, Nuxt provides the following key features:
- Automatic transpilation and bundling
- Hot module replacement
- Server-side rendering OR Single Page App OR Static Generated, you choose 🔥
"Automatic server rendering and code splitting" is the top reason why over 9 developers like Next.js, while over 12 developers mention "SSR" as the leading cause for choosing Nuxt.
Next.js is an open source tool with 38.7K GitHub stars and 4.7K GitHub forks. Here's a link to Next.js's open source repository on GitHub.
CircleCI, Avocode, and SeatGeek are some of the popular companies that use Next.js, whereas Nuxt is used by Bitupper, Quero Education, and Compile Inc. Next.js has a broader approval, being mentioned in 82 company stacks & 69 developers stacks; compared to Nuxt, which is listed in 51 company stacks and 52 developer stacks.
My backend set up is Prisma / GraphQL-Yoga at the moment, and I love it. It's so intuitive to learn and is really neat on the frontend too, however, there were a few gotchas when I was learning! Especially around understanding how it all pieces together (the stack). There isn't a great deal of information out there on exactly how to put into production my set up, which is a backend set up on a Digital Ocean droplet with Prisma/GraphQL Yoga in a Docker Container using Next & Apollo Client on the frontend somewhere else. It's such a niche subject, so I bet only a few hundred people have got a website with this stack in production. Anyway, I wrote a blog post to help those who might need help understanding it. Here it is, hope it helps!