Object literal may only specify known properties, and 'mdi' does not exist in type

[Maxttier]

vuetify: {
    vuetifyOptions: {
      icons: {
        defaultSet: 'mdi',
        aliases,
        sets: {
          custom,
          mdi,
        },
      },
    },

Object literal may only specify known properties, and 'mdi' does not exist in type 'IconFontName[] | FontIconSet[]'.ts(2353)
(property) mdi: IconSet

https://nuxt.vuetifyjs.com/guide/
https://vuetifyjs.com/en/features/icon-fonts/#usage

[Maxttier]

[{ name: 'mdi'}, { name: 'custom', ???????????????}

[Maxttier]

Object literal may only specify known properties, and 'aliases' does not exist in type 'IconsOptions'.

[Maxttier]

interface IconsOptions {
    /**
     * @default 'mdi'
     */
    defaultSet: IconSetName;
    /**
     * The prefix for UnoCSS Preset Icons.
     *
     * @default 'i-'
     */
    unocssIconPrefix?: string;
    /**
     * Override the default mdi icons.
     *
     * Icon names should include the prefix and the collection, for example:
     * - home: i-<collection>:<icon>
     */
    unocssIcons?: UnoCCSMdiIconSet;
    unocssAdditionalIcons?: Record<string, string>;
    sets?: IconFontName | IconFontName[] | FontIconSet[];
    svg?: {
        mdi?: JSSVGIconSet;
        fa?: FontAwesomeSvgIconSet;
    };
}

[AndreyYolkin]

Moving this to the 2.0.0 milestone (the statically-analysable config rewrite). This is the same root cause as #72: the module's icons.sets is a font-import shorthand (IconFontName | IconFontName[] | FontIconSet[]), not Vuetify's Record<string, IconSet> object map, and the static config can't express function/component aliases (IconValue) — both are inherent to the current Vite-plugin + JSON-serialization architecture.

In the v2 rewrite (see vuetify-nuxt-module-nuxt-v4), configuration moves to a real vuetify.config.ts via defineVuetifyConfiguration, so you pass native Vuetify icon options directly — object-map sets and function/component aliases work as documented. That resolves both #293 and #72 at the source rather than via a 1.0.0 type patch.