Nuxt 3.12.2 ignores vuestic.config.ts

[m0ksem]

v3.12.1 works fine

Repro: https://stackblitz.com/edit/github-poqjmh?file=package.json,nuxt.config.ts,app.vue

when component used via auto-import it ignores vuestic.config.ts

Although, if component is imported from 'vuestic-ui' via import config is applied correctly.

Looks like nuxt imports from esm-node build when registering global components, instead of es since 3.13.2

may be related to: https://github.com/nuxt/nuxt/pull/28843/files#diff-06cc43bd13b65d1b07374d99f41947196c616c32398339ed40d0a3faa678ad2dR174

Now when nuxt ensures filePath, resolvePath from mlly uses node condition with higher priority.

We could replace component registration with absolute path manually.

  import { resolveSync } from 'mlly'

  const vuesticModulePath = resolveSync('vuestic-ui', {
    conditions: ['import'],
    url: import.meta.url
  })

  importNames.forEach((name) => {
    /**
     * Add component from vuestic-ui package.
     * Nuxt will tree-shake components that not included in options.
     * Nuxt also will add component to auto-import.
     */
    addComponent({
      name,
      export: name,
      filePath: vuesticModulePath
    })
  })

[m0ksem]

After resolvePath force added, nuxt loads components from different places:

• When component is global, because path was resolved with mlly, it is path to node_modules:

  import {VaButton as __nuxt_component_0} from "/_nuxt/node_modules/.pnpm/vuestic-ui@1.10.3_vue@3.5.12/node_modules/vuestic-ui/dist/es/main.js?v=0e702035";

• When loaded via import, path is set to vite cache.

  import {VaButton as ImportedButton, useGlobalConfig as useImportedGlobalConfig, } from "/_nuxt/node_modules/.cache/vite/client/deps/vuestic-ui.js?v=6d032d21";

Initially, I though problem in incorrect condition exports in vuestic package.json (fixed in #4404), but eventually I noticed that import * from 'vuestic-ui' resolves import from vite cache.