Kael

Results 390 comments of Kael

It's a vue bug really. `loadIconComponent` resolves while vue is rendering other components, so `__restore` sets `currentInstance` back to NuxtIcon when `normalizeSlot` is expecting it to be null. https://github.com/vuejs/core/blob/a95e612b252ae59eaf56e0b8ddba66948d4ac20e/packages/runtime-core/src/apiSetupHelpers.ts#L521 ![Screenshot_20230629_173421](https://github.com/nuxt-modules/icon/assets/16421948/0d449e10-00d3-4b36-b7f6-4d08b0d8a35d)

Not sure what happened here, it seems to be working now.

This plugin is only really intended to be used for migration from v2-v3, not for existing v3 projects.

`:text="variable"` is replaced with `:variant="variable && 'text'"` so it isn't really possible to have a rule that works for both

Not variables. Static strings is possible, the way rules are defined internally though is just `text: { name: 'variant', value: 'text' }` which is also shared with other props so...

Another option would be something like `settings.vuetify.migrationMode = false` https://eslint.org/docs/latest/use/configure/configuration-files#adding-shared-settings

Too aggressive, the existing rule already breaks certain object slots.

No plans to add this to the v2 plugin.

Is this still relevant?

Does vue-i18n 8 even work with vue 3? > I figured that it would be true to its name. It just means that if it's installed it should match a...