vite-plugin-pwa VS vite

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

For the frontend of "I Disappear," I leverage the automated build & deploy system provided by Netlify, which seamlessly integrates with Vite. This setup ensures that every deployment is optimized for performance, utilizing Vite’s modern build tools to enhance speed and efficiency.

Given our team's collective proficiency within the React ecosystem, we decided to leverage this expertise for our project. Initially, we contemplated utilizing Next.js; however, due to the limited practical experience with this technology among key engineers and the pressing timeline to develop the first prototype, we opted for a Single Page Application(SPA) approach. For bundling, we selected Vite, primarily due to its super fast build times, simplicity of configuration, and potential for a nearly seamless transition to server-side rendering.

We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.

Vite focuses on providing an extremely fast development server and workflow speed in web development. It uses its own ES module imports during development, speeding up the startup time.

Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react-swc' import path from 'path' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 3000 }, css: { devSourcemap: true }, resolve: { alias: { '~': path.resolve(__dirname, './src') } } })

I am currently utilizing Vite:

Homepage: https://vitejs.dev/

Without any adding any dependencies you can connect react props to raw css at runtime with nothing but css variables (aka "custom properties"). If you add CSS modules on top you don't have to worry about affecting the global scope so components created in this way can be truly modular and transferrable. I use this with vite.

Little confused as to why it has vite in it‘s name, it seems unrelated to https://vitejs.dev/