language-tools: Bug: Auto import from vue adds separate import statements in .vue files

Vue - Official extension or vue-tsc version

2.1.2

VSCode version

1.92.2

Vue version

3.4.38

TypeScript version

5.5.4

System Info

No response

Steps to reproduce

This happens only in .vue files, works ok in .js files.

Every time I use auto import from ‘vue’, the symbol I select is imported in a separate import statement (separate line), resulting in multiple import { ... } from 'vue' statements.

Note: I already reported this issue to VSCode devs (https://github.com/microsoft/vscode/issues/227042) but they said it’s Vue related and should be reported here.

VSCode Extensions (19)
Extension Author (truncated) Version
project-manager ale 12.8.0
npm-intellisense chr 1.4.5
path-intellisense chr 2.9.0
js-codeformer cms 2.6.1
vscode-eslint dba 3.0.10
gitlens eam 15.3.1
EditorConfig Edi 0.16.4
prettier-vscode esb 11.0.0
html-slim-scss-css-class-completion gen 1.7.8
JavaScriptSnippetsStandard jms 1.8.0
remote-ssh ms- 0.113.1
remote-ssh-edit ms- 0.86.0
remote-explorer ms- 0.4.3
abracadabra nic 9.4.6
material-icon-theme PKi 5.10.0
vscode-yaml red 1.15.0
volar Vue 2.1.2
vscode-todo-highlight way 1.0.5
material-theme zhu 3.17.2

What is expected?

Expected result is to reuse the 1st import statement and add the symbol there.

What is actually happening?

Here is the state before I auto-import the second symbol from vue: image And here is what happens immediately after I hit Enter on the computed symbol: image

Link to minimal reproduction

No response

Any additional comments?

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 2
  • Comments: 24 (8 by maintainers)

Most upvoted comments

I have same issues with auto import in Nuxt

Does changing jsconfig.json to tsconfig.json resolve your problem?

There seems to be a regression. Nuxt auto-imports are not working in 2.1x