Closed piotr-cz closed 1 year ago
Name | Link |
---|---|
Latest commit | 34687671f2712ce6b979a768676a8adef5b8c413 |
Latest deploy log | https://app.netlify.com/sites/vite-pwa-org/deploys/63b95aa414298600094c4852 |
Deploy Preview | https://deploy-preview-17--vite-pwa-org.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
uhmm, when using generateSW
strategy, workbox-build
will generate sw.js
and workbox-xxx.js
in the output build folder, the file you mention is the client side of the pwa plugin (the virtual module imports workbox-window
using dynamic import).
sw.js
imports workbox-xxx.js
, the service worker utilities from workbox-build...
@userquin
You are correct, I've tested only for injectManifest
strategy. Thank you for detailed explanation!
The
workbox-window.prod.es5.[HASH].js
file is being generated by vite insideassets
directory, There are no files generated matching above glob in dist directory.There is no need for special cache directive, caching is already covered by
location ^~ /assets/
block.