Open R0N1n-dev opened 1 year ago
@R0N1n-dev workbox-build only works in one mode, if you are using custom sw (injectManifest strategy), you MUST include runtimeCaching
in your service worker logic, check this for example: https://github.com/elk-zone/elk/blob/main/service-worker/sw.ts#L56-L94
Those entries are the equivalent to your workbox.runtimeCaching
handler: when using generateSW
strategy, workbox-build will generate a registerRoute
per plugin in the sw output.
In summary, when using generateSW
workbox-build will be configured using workbox
pwa plugin configuration entry; when using injectManifest
strategy workbox-build will be configured using injectManifest
pwa plugin configuration entry.
I really wish you guys wouldn't close the issue b4 confirmation that ur proposed solution is working, because it is not and now i will reopen it till i get a working solution
Upps sorry, wrong button...
I really wish you guys wouldn't close the issue b4 confirmation that ur proposed solution is working, because it is not and now i will reopen it till i get a working solution
I really wasn't trying to be rude, maybe u imagined me screaming the words but its just an honest observation that i have dealt with alot when posting issues on github.
Cannot seem to get runtime caching to allow for caching of api data.
vite.config.js
sw.js