Joaquín Sánchez
Joaquín Sánchez
If you have a monolitic module with disparate dependencies, you will be able to use it in some environments. For example, your app Will not work on node server if...
@nodegin I still don't know what's failing, building the app, building the sw or running the app build?
@nodegin you need to split your library, I've done these changes: - add `sw-stuff.ts` in your library, exporting only `test` - re-export all sw stuff on index.ts: `export * from...
@adam-lynch - using `cleanupOutdatedCaches` has the problem of a hard refresh on client side, we're using stale while revalidate strategy (html pages on cache with old assets versions, missing from...
@adam-lynch in theory, workbox-build will try to update changed assets, if the quota is reached, browser can remove assets without any logic, so beware assuming what resources/assets will be evicted....
on quota error the sw will no install/activate the new sw and so your new app version (or maybe unpredictable behavior, it will depend on user agent and/or OS): you...
Upps sorry, it was here https://web.dev/i18n/en/storage-for-the-web/#over-quota EDIT: You can use plugins with `generateSW` strategy, you don't need to switch to build your own service worker
check this: https://github.com/vitest-dev/vitest/blob/main/docs/vite.config.ts#L86 Beware with opaque responses (CORS)
@adam-lynch I'm adding a new entry in deploy section https://github.com/vite-pwa/docs/pull/19
@adam-lynch can this be closed?