New Vite Service Worker Plugin about chromeos.dev HOT 10 CLOSED

Thanks to the above comments, and a rethink of how we may implement our SW, I think our implementation can move from creating a new SW plugin to improving how we use Vite PWA today. There are still some areas (like local development) where there is work needed, but we can survive without it right now.

from chromeos.dev.

May icebox this if vite-pwa/vite-plugin-pwa#192 lands

from chromeos.dev.

@Snugug I'm also interested on trying to fix this list, we can fix it, PR are welcome on the plugin, some hints:

1. you can use globPatterns and globIgnores
2. I need to review the plugin, but I think you don't need to use the virtual module virtual:pwa-register (using workbox-window)
3. uhmm, maybe we can add another strategy for it, since the service worker is compiled, we only need to omit the injectManifest part
4. I think this option should be done via vite configuration
5. I have some branch on my fork with some tests to allow test on development.

from chromeos.dev.

@Snugug the repo and branch for sw on development can be found here https://github.com/userquin/vite-plugin-pwa/tree/feat/add-development-support

Just check the last plugin on src/index.ts module and the logic on src/dev.ts module.

from chromeos.dev.

@Snugug you can use injectRegister: null for entry 2, see description here: https://github.com/antfu/vite-plugin-pwa/blob/main/src/types.ts#L47

from chromeos.dev.

for 1) you can also use transformManifest

from chromeos.dev.

FYI: working on a new strategy to compile custom sw

from chromeos.dev.

@Snugug just check this jeffposnick/yt-playlist-notifier#2, using custom sw on development

from chromeos.dev.

@Snugug pwa plugin released 0.11.13 with development support

from chromeos.dev.

@Snugug do you need to build only the service worker without injectManifest?

from chromeos.dev.