Skip to content

Vue + Astro extension conflict: no auto-import suggestions in Vue template prop expressions #15962

@apvd79

Description

@apvd79

Astro Info

Astro                    v6.0.5
Vite                     v6.4.1
Node                     v25.8.0
System                   macOS (arm64)
Package Manager          npm
Output                   static
Adapter                  none
Integrations             none

If this issue only occurs in one browser, which browser is a problem?

n/a

Describe the Bug

When the Astro VS Code extension (astro-build.astro-vscode) is active alongside Vue - Official (VO), auto-import suggestions stop working in Vue <template> prop/attribute binding expressions. No crash, no error — suggestions simply don't appear.

Auto-imports work in <script setup> and when typing into open tags in the template — only prop binding expressions are affected. Disabling the Astro extension resolves the issue completely.

The conflict is one-directional: enabled Astro extension's presence breaks VO's template prop completions, but Astro's own template completions are unaffected when VO is enabled.

Same class of Volar.js decorator conflict described in vuejs/language-tools#3942 (Vue + Svelte)?

vscode-bug.mov

Steps to Reproduce

  1. Install both Vue - Official (v3.2.5) and Astro (v2.15.x) extensions
  2. Clone the repro, run npm install, open in VS Code
  3. Open src/App.vue
  4. Place cursor inside the :icon="" prop on the <FontAwesomeIcon> component
  5. Type faL — no suggestions appear

Apologies if I missed anything, happy to clarify or correct if needed.

Also opened on the Vue extension repo: vuejs/language-tools#6000

Thanks!

What's the expected result?

Auto-import suggestions should appear in prop binding expressions, matching the behavior in <script setup> and open tags.

Link to Minimal Reproducible Example

https://github.com/tworonin/vue-astro-vscode

Participation

  • I am willing to submit a pull request for this issue.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions