purgecss VS Nuxt.js

As a starting point, Tailwind used to use PurgeCSS [0] but I'm not sure what they use now.

[0] https://purgecss.com

A similar question was already posted here but, I think looking at the raw html, we will be able to better determine the required css than what Purgecss does.

PurgeCss

Webpack minifies JS and CSS files by default when we build them in production mode. But it does not remove useless styles or classes. For this, you can use libraries like https://purgecss.com/ Do not forget to check the dependency, connect only the functionality that you use.

When I searched online I couldn't find an "industry standard" solution to this problem. What I ended up doing was using the popular tool PurgeCSS along with a quick Python script to generate the appropriate command. What the PurgeCSS tool does is search for all your HTML files, gather all the CSS classes used, and then "purge" all the unused ones from the CSS file. You just need to declare all the HTML files you have.

Skeleventy gives you a rock-solid foundation to build fast and accessible static websites, with clean, understated design. Features include a minimal build pipeline with Laravel Mix, the Sass-powered utility class generator Gorko, Purge CSS, an HTML minifier, SEO-friendly page metadata, image lazy loading, responsive navigation, and an XML sitemap.

You could look into using PurgeCSS and its cli?

Unable to get rid of unused styles. Importing components individually and setting styles in SASS can greatly simplify builds, but several common unused styles can't be deleted using PurgeCSS and analogues due to dynamic class names.

If you’re hand-crafting your CSS, using only the exact classes you need, you’ll still probably find that your CSS file size grows as your site does. But it doesn’t need to grow too much — you can remove unused classes with tools like Purge CSS .

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.