vite-plugin-pwa VS nx

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

One notable feature is the ability to remember selected tabs. When you select a specific tab on a page, all other tabs on the page with the same name will also be selected. This selection will persist during your next visit to nx.dev.

Hono does have a template application for Vercel, but in my case, my requirements were different (aren't they always 😅). I was working in a monorepo (using nx) because I wanted to manage my libs, tests, and examples all together in a single place, instead of having different repos.

Recently, My coworker is using Nx to automate his workflow, including automated release using semantic version. I found this method quite useful, so I want to re-implement on single GitHub repositories (without Nx).

I started a discussion on GitHub concerning that subject: Design Nx Plugin Project Crystal

Nx

We are looking for companies to partner with on the Analog project to support development of the project. Thanks to Snyder Technologies for being an early adopter and promoter of Analog, Nx for joining us as a sponsor, House of Angular, and many other backers of the project.

Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI.

The advent of esbuild, the native support for ES Modules in browsers, the widespread adoption of import map, the emergence of tools like Native Federation, and the Nx ecosystem all combine to forge a flexible and well-maintained Micro Frontend Architecture.