vite-plugin-pwa VS purgecss

I am trying to glue together a Nuxt 3 PWA with vite-plugin-pwa, more specifically @vite-pwa/nuxt. I installed the module and set up basic configuration (I basically followed this video)

Depends on your needs for storing app data and will you persist that data too? Supabase and Nuxt go really well together but if you are needing to store data in supabase's postgres database I'd high recommend adding Prisma to your stack as well. You may already have this too the but nuxt pwa module is a great way to get setup as well: https://vite-pwa-org.netlify.app/ I've built a couple of ecommerce headless shopify shops and a couple of sites with Nuxt 3 so far and am loving the dev experience with it. But I'm by no means and expert too. YMMV.

All you need to make a Vite app into a PWA is this: https://github.com/vite-pwa/vite-plugin-pwa

PWA is created with vite-pwa/vite-plugin-pwa, and its parameters are set in vite.config.js. In summary, the implementation of PWA was not a project aim, but it did provide good caching of all project components and resulted in a very quick reopening of the site.

vite-plugin-pwa

I'm afraid that I can't help you since I don't have much experience in creating my own service worker. Instead, I'm using a library that helps me with that. This is the library I use on my project, and it works pretty well in updating the service worker. Although it is built for Vite, the fundamental logic should be the same.

I’m particularly fond of the pwa plugin AntFu did with vite-plugin-pwa.

I recently switched my app to use Vite instead of CRA, along with that I started using vite-plugin-pwa to manage the service worker of my app, and it has been working like magic. Even with my app being served behind a cache in Cloudfront, whenever I deploy I wait 20 seconds and it suddenly starts fetching the new bundle. You can cofigure it to automatically reload the page, or to notify the user when there is an update available to reload.

Hey there, have a look at the examples

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 .