Joaquín Sánchez

you use latest (sharp and sharp-ico) using `resolutions` in your package.json, my OS is Windows, I cannot test/run `bun` on my local :cry:

Once added dependency `yarn add -D eslint-plugin-vuetify`, there are some errors on `yarn serve`: ```shell F:\work\projects\quini\vuejs\vuetify-preset-test>yarn serve yarn run v1.16.0 $ vue-cli-service serve INFO Starting development server... 40% building 26/29...

For `eslint-loader` error, just configure these rules to `.eslintrec.js` (https://github.com/babel/babel-eslint/issues/681#issuecomment-420663038): ```js rules: { 'no-console': process.env.NODE_ENV === 'production' ? 'error' : 'off', 'no-debugger': process.env.NODE_ENV === 'production' ? 'error' : 'off', 'template-curly-spacing'...

There are some ts errors in the tests: `task-queue.test.ts` and `uncaught-exception-from-handler.test.ts`

You should add package exports to your package.json, this package seems to be CJS only... https://arethetypeswrong.github.io/?p=unplugin-primevue-resolver%401.0.3

The sw scope needs to be there at build time, the webmanifest and the sw registration are built at runtime, we can bypass the problem in the sw registration but...

Remove file extensions from globPatterns, for example, you can remove `mp3` and `mp4` extensions, then add a new runtime caching handler: ```ts { urlPattern: ({ url, sameOrigin }) => sameOrigin...

@houtan-rocky can you try adding a custom sw importing this module on it? It is a custom `msw/mockServiceWorker.js` registering logic when `import.meta.vitest` is present (if not using Vitest you will...

For example, using `@vite-pwa/create-pwa` with inject manifest (the `prompt-sw.ts` should be `sw.ts`): 

I don't use Brave, I always use Chrome/Chromium in my sw tests (including Android Device via USB). Check this entry https://docs.elk.zone/pwa#debugging-pwa-in-mobile-browsers and this tweet https://twitter.com/userquin/status/1606967107325165570