Sapper VS Nuxt.js

I built my first simple blog site in 2020 using Svelte and Sapper. The blog posts were powered by markdown files stored in the repository, and it was a great starting point.

Sapper

pancake which has very scarce documentation and is in thorough experimentation(at the time of writing). Since it has been created by Rich Harris, you can rest assured that it might probably never get documentation or a stable release just like our fallen soldier sapper (a moment of silence in remembrance)

You might also want to check out Sapper, a framework built on Svelte that allows you to develop more advanced features like server-side rendering, offline support, and file-based routing.

Does this help https://github.com/sveltejs/sapper/issues/343

SvelteKit can be considered the successor to Sapper or NextJS for Svelte. It is packed with tons of cool features, like server side rendering, routing, and code splitting.

So after using Sapper for some time, I decided to move my website to SvelteKit. I remember saying that I would not move to SvelteKit till they hit version 1 but the framework looks too promising. It had features which I needed and those features weren't in Sapper.

By that time, we had some troubles with virtual dom itself in our custom rich text editor that we based on slate - it was getting a bit laggy when creating huge financial documents (they usually have enormous tables and a lot of infographics) -so we were already thinking about other options and that’s where svelte comes into the light - especially sapper which was de facto default framework to be used with svelte at that time (SvelteKit wasn’t even announced).

Sapper is a framework for building web applications of all sizes, with a beautiful development experience and flexible filesystem-based routing. It is the predecessor of Sveltekit.

According to Node Package Manager (NPM), Next.js has about 3.9 million weekly downloads while Nuxt.js has about 438,000. Although Next.js has a significantly higher number of weekly downloads, Nuxt.js still has a robust number of users. We can conclude that both frameworks are relevant and will stand the test of time.

Nuxt team themselves pointed that out [in first release](https://www.npmjs.com/package/nuxt/v/0.0.1) as well as you can see that statement in [Nuxt's wikipedia article](https://cdn.domin.pro/K2Qa). I completely agree with how Nuxt is better for an amount of features.

Node is basically back-end Javascript. While powerful alone, almost exclusively you will use a back-end framework like Next.js or Gatsby when using React, and then maybe Nuxt or Gridsome in Vue.

Both Vue.js and React have their own set of tools and libraries to help developers build and maintain their applications. Vue.js has Vue CLI and Nuxt.js, while React has Create React App and Next.js.

Nuxt.js is a free and open-source JavaScript framework based on Vue.js that helps you develop modern web applications using SSR (server-side rendering) which provides a faster load, better SEO (search engine optimization), and better caching capabilities.

We made a LiveChat Next.js App template. Using Next.js as a foundation for the project, we have a front-end app with built-in routing, Server Side Rendering (SSR), and Server Side Generation (SSG) built with React, but on top of that, ready-to-use API routes built in the form of Serverless functions. If you prefer Vue.js or Svelte, you can choose similar frameworks, like Nuxt.js and SvelteKit.

Not oc, but maybe give Nuxt a look?

Vue's docs are some of the best I've ever read. Nuxt and Craft are pretty great too. I especially like how Craft's docs are bifurcated into the docs which give you the 20/80 + code snippets, and the class reference, which is complete documentation of every method, type, param, etc of the platform.

Nuxt - the Vue alternative to NextJS - supports both static site generation and SSR.