Do we need to add "cleanupOutdatedCaches: true"

[muktihari]

When we deploy an update, I think I need to refresh the page several time before the updated data is loaded properly. Does adding "cleanupOutdatedCaches: true" in "workbox" will help us achieve the immediate auto update without refreshing the page? Currently we don't specify the prop:

openivity.github.io/vite.config.ts

Lines 29 to 39 in e305f58

	workbox: {
	globDirectory: 'dist',
	globPatterns: ['**/*.{js,css,html,ico,wasm,svg,ttf,woff2}'],
	maximumFileSizeToCacheInBytes: (1000 * 10) << 10, // 10MB per file
	runtimeCaching: [
	{
	urlPattern: new RegExp('^https://.*\\.openstreetmap.org/.*\\.png$'), // cache osm tiles.
	handler: 'CacheFirst'
	}
	]
	}

In this documentation, https://vite-pwa-org.netlify.app/guide/auto-update.html#cleanup-outdated-caches, says it's enabled by default, but in code doc it says otherwise: false. 😢

Any idea @raditzlawliet ?

[raditzlawliet]

Hmm... I check out the web is have max-cache: 600. And every time we build, it always re-generate file with new name. That's why it should be fine for usual web.

But currently we use PWA to make cache and can be access when offline.
I re-read again, we need to add them unless if we're using generateSW strategy.

Try that options manually set true.
I also read something about background sync configuration, may can help https://vite-pwa-org.netlify.app/workbox/generate-sw

[muktihari]

I see, I'll send a PR to set cleanupOutdatedCaches: true first. Currently, I don't have time to change it into generateSW as I need to read more about it first and then still need to re-test it again, unless we really need it. But PR are welcome tho 😅