Vue Official extension Language Server fails to start — "Go to Definition" unavailable for .vue files

[pkbdemo]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

win32

Kiro Version

0.11.133

Bug Description

Environment

• Kiro version: Latest (as of 2025-04-29)
• OS: Windows
• Vue Official extension version: Latest (also tested with older versions)
• TypeScript version: 6.0.2 (installed in project)
• Vue version: 3.2.7

Description

The Vue Official (Vue.volar) extension is installed and shows as "Enabled" in the Extensions panel, but its Language Server never starts. This causes all Vue-specific language features (Go to Definition, auto-complete, type checking, etc.) to be completely unavailable for .vue files.

This was working normally last week and stopped working without any changes to the project configuration.

Actual Result

• Error message appears: "Go to Source Definition failed. Unsupported file type." with source labeled as "TypeScript and JavaScript Language Features"
• The right-click context menu does not show "Go to Definition" for .vue files
• The Output panel dropdown does not contain "Vue Language Server" or "Vue" — the Language Server is not running at all
• The command palette does not show "TypeScript: Restart TS Server" (though TS works for .ts files)

What I've Tried (all unsuccessful)

1. Developer: Reload Window
2. Disable and re-enable the Vue Official extension
3. Downgrade Vue Official to an older version
4. Toggle vue.server.hybridMode between true and false
5. Verified .ts files have working "Go to Definition" — TypeScript Language Service itself is functional

Workspace Settings (.vscode/settings.json)

{
    "dotnet.defaultSolution": "projects.sln",
    "[vue]": {
        "editor.defaultFormatter": "esbenp.prettier-vscode"
    },
    "typescript.tsdk": "UP.FrontEnd/node_modules/typescript/lib",
    "vue.server.hybridMode": false
}


### Steps to Reproduce

1. Open a multi-project workspace containing a Vue 3 + TypeScript project (e.g., a subfolder like `UP.FrontEnd/` with `tsconfig.json` and `.vue` files)
2. Ensure the Vue Official extension is installed and enabled
3. Open any `.vue` file
4. Right-click on a function or variable name, or press `F12`

### Expected Behavior

- Vue Official Language Server should start and appear in the Output panel
- "Go to Definition" should work in `.vue` files, navigating to the correct source

### Conversation ID

7464a0a1-78c5-4d70-8982-ee05f2a6963e
7464a0a1-78c5-4d70-8982-ee05f2a6963e
7464a0a1-78c5-4d70-8982-ee05f2a6963e

### Additional Context

_No response_

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #5977: PHP LSP fails to initialize - no autocomplete for .module/.inc files (85% similar)
• #5531: Prompt indicator λ lost after /chat load or /chat resume — cannot recover without full restart (85% similar)

What happens next?

• ⏰ This issue will be automatically closed in 3 days
• 🏷️ If this is not a duplicate, you can prevent automatic closure by adding a comment or reacting with 👎 to this message.
• 💬 Comment on the original issue if you have additional information

Why is this marked as duplicate?
Both report language server initialization failures causing loss of language features like autocomplete and go-to-definition, though one affects PHP LSP and the other affects Vue Language Server

[zeng-ge]

the same issue appeared after update kiro to Version: 0.11.133

[github-actions]

Thank you for your feedback! 🙏

The duplicate label has been removed and this issue has been sent back for maintainer review.

A maintainer will review this issue shortly.

[Rochester-Ting]

the same issue appeared after update kiro to Version: 0.11.133