Joaquín Sánchez
Joaquín Sánchez
@bimohxh it is the way the New sw will control again the app once new version cache ready, check sw lifecycle
@bimohxh I wrote previous code, if you dont reload the window the new sw will not control the page that is being controlled by the current sw version (old one),...
@bimohxh then use prompt for update strategy, other logic is when there are other clients and the update comes from them.
@bimohxh if you only want the sw to get updated you will need to remove any virtual from your code, Safari users will have problems using the PWA (previous sw...
check the warning here: https://vite-pwa-org.netlify.app/guide/auto-update.html#automatic-reload
This package is not a bundler, the images should be in the same place, you generate the images once. You can move the generated images where you want using releative...
> * The web app manifest should specify `purpose: "any"` on images that are not `maskable` . There is no need since `any` is the default value: https://developer.mozilla.org/en-US/docs/Web/Manifest/icons
> * IMO you don't need an `ico` file in the `minimal-2023` preset when you can serve a `png` file instead. [It is very well supported](https://caniuse.com/link-icon-png). You don't need png...
> * The web app manifest should also link to the original SVG. The SVG is the best logo to use if the client supports SVG. Why? Not all browsers...
You can add the favicon you want since this package will not add anything to your html pages, you can generate any png image with any resolution and add the...