Joaquín Sánchez
Joaquín Sánchez
This is a problem in both, workbox-build and sentry when using `generateSW` strategy: - you cannot use type module in non chromium based browsers when registering the sw - generateSW...
@mydea the problem is about testing the sw and the pwa web manifest, sentry should have a way to exclude some assets, rn any asset with `js/ts/jsx/tsx/mjs` extension being intercepted...
EDIT: or just exclude the sentry plugin in dev, it is easy, just adding `apply: 'build'` when exposing the unplugin plugin for vite.
@lforst `workbox-build::generateSW` will build the sw using `importScripts` and we cannot use ESM `import` syntax when registering the sw using `type: 'classic'` (rn only chromium based browsers support `type: 'module'`...
Vite plugin pwa supports dev mode https://vite-plugin-pwa.netlify.app/guide/development.html
I'm going to close this PR and send it again from remix repo.
Check https://vuetify-nuxt-module.netlify.app/guide/icons/svg-icons.html and https://vuetify-nuxt-module.netlify.app/guide/icons/integrations.html
If the question is about using it with `v-icon` you should ask in `vuetify` repo.
Check any repo here: https://vuetify-nuxt-module.netlify.app/guide/icons/integrations.html Basically `v-icon` accepts an string or a component, it just renders it: `@mdi/js` just exports the svg icons as js objects, then `v-icon` just renders...
just import the icon you want: `import { mdiArrowDownRight, mdiFormatQuoteOpen, mdiArrowRight } from '@mdi/js'`