Joaquín Sánchez
Joaquín Sánchez
@likeadeckofcards the output folder is set by the vite laravel plugin, we cannot undo the hacks done by that plugin; filter issues with laravel, there are some workaround to make...
@likeadeckofcards the laravel plugin is setting the Vite outDir to that folder, check my comment in this issue https://github.com/vite-pwa/vite-plugin-pwa/issues/467#issuecomment-1427998051
I use Windows 10 PRO and all examples in the repo working (also the tests). Provide a minimal repro or at least pwa configuration...
you need to run the preview script, running build will build the app but running `vite` will start the dev server, add this script and run it: `"win-start-preview": "vite build...
dev options only to test web manifest and custom sw logic (injectManifest strategy), you should disable dev options once tested web manifest
I think you are mixing concepts, you don't need HMR (which you only have it in development) to test your application offline, just run the build + preview script and...
https://vite-pwa-org.netlify.app/guide/periodic-sw-updates.html
when developing, Vite will update the app via HMR EDIT: remove the service worker once you disable dev options
I guess we should add it to custom injectManifest configuration option, this way we can inject the query params in the client and use it also on src/plugins/dev.ts plugin, check...
There should be only one source, if we add the option to the client side, dev will not work. > If we add query params as a property to CustomInjectManifestOptions,...