Intellisense for vue is broken

[TheDutchCoder]

Bug Report

🔎 Search Terms

intellisense, vue, import

🕗 Version & Regression Information

• This changed between versions [unknown] and version: 1.60.2

⏯ Playground Link

N/A

💻 Code

// Current, broken behaviour
export default defineC // intellisense will suggest `defineComponent` from @vue/runtime-core

// Old, correct behaviour
export default defineC // intellisense will suggest `defineComponent` from vue

🙁 Actual behavior

TS resolves any Vue export from its submodule, instead of the main vue package

🙂 Expected behavior

TS to resolve from vue

[Shinigami92]

But only for Vue 3 please... ?!

In Vue 2 it should be

export default defineC // intellisense should suggest/prefer `defineComponent` from @vue/composition-api instead of `vue` or `vue-demi`

[sandersn]

What version of Typescript is this? Is this vue 1.60.2? vs code 1.60.2?
Can you provide an example repo?

[Shinigami92]

Nathan Shively-Sanders (@sandersn)

What version of Typescript is this? Is this vue 1.60.2? vs code 1.60.2?

VS Code 1.60.2

Vue is in Version 2.x or 3.x, 1.x is completely outdated.

[andrewbranch]

// Current, broken behaviour
export default defineC // intellisense will suggest `defineComponent` from @vue/runtime-core

Is this example right? Why would we suggest any auto-imports at export default? IMO we should only show locals there. The general issue of the auto-import coming from the wrong place is almost definitely a duplicate of #45784 and fixed by #45792.

[andrewbranch]

Can anyone try this with typescript@next and see if the problem persists? (https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-typescript-next)

[henribru]

Just tried it with v4.5.20211015 and VS Code is still importing defineComponent from @vue/runtime-core

[lukaskleinschmidt]

Andrew Branch (@andrewbranch) It is working for me with typescript@next in a regular .js file.
In SFC it still doesnt work, but honestly I have no idea whether this is more of a Vetur or Volar problem?

[andrewbranch]

Should be fixed by #46437

[xd-shadow]

so has the problem been fixed? it is still exists with me