auto-import inconsistencies within template

[theoephraim]

Having some funky behaviour around auto-import suggestions only within vue templates, which leads me to believe it is a volar issue. The issue is that in the script section of a vue file (or other .ts files) importing a component that is exposed via an index file works correctly, while within the template block, the import suggestion is to import from the file directly.

Correct behaviour (within script block)

Incorrect behaviour (within template tag)

I'm unclear on what scenarios this occurs, but in my case specifically, the module @si/ui-lib is a shared component library within the monorepo, and is being used directly without being built first - meaning

my web app's package.json includes the dependency via pnpm workspace linking

"@si/ui-lib": "workspace:*",

and @si/ui-lib's package.json exports the ts files directly

"main": "src/index.ts",
"types": "src/index.ts",

the index file just re-exports the components, for example

export { default as CoolButton } from './components/CoolButton/CoolButton.vue';

I have tried many different iterations of tsconfig files using aliases, project references, etc... What I have now seems to work the best and be very simple, with the only issue being this auto-import in vue templates.

Let me know if you need a minimal repro and I'll set one up.

Cheers!

[louia]

The component/function autocomplete feature not work actualy.

I use Typescript with TakeOver with vue 3.2 on the latest version of vscode.

If there is no import of the library into the project, volar does not recognize the library. You have to import your component manually for the first time and then the auto-import will work as expected.

BUT if you remove all the imports to the lib you will have a error like this in the suggestions window :

I don't understand that volar can't analyze the dependencies in the node_modules to propose the autocompletion of the imports

Is this a bug?