It seems like OpenCode don't see TypeScript errors in Vue files #8402

Open
opened 2026-02-16 18:09:52 -05:00 by yindo · 2 comments
Owner

Originally created by @it-sha on GitHub (Feb 3, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

I'm trying to check that OpenCode really sees the TypeScript errors in files via LSP
Becouse regular npm run type-check takes around 10min in project

Do we have a reliable way to check that LSP diagnostics are working?

Prompt like

give me a list of TypeScript errors in this file.
Just run npm run type-check.

If I'm using prompts like

use LCP diagnostics to get TypeScript errors
I see a response I don't have access to any LCP diagnostics

Plugins

No response

OpenCode version

1.1.49

Steps to reproduce

  1. Create a vue file with ts error e.g.
<script setup lang="ts">
const test: string = 1
console.log(test)
</script>

<template>
<div>hello</div>
</template>
  1. Run propmpt give me a list of TypeScript errors in this file
  2. See that response do not use LSP

Screenshot and/or share link

/status after reading Vue file

Image

Operating System

Windows 11 with WSL

Terminal

bash

Originally created by @it-sha on GitHub (Feb 3, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description I'm trying to check that OpenCode really sees the TypeScript errors in files via LSP Becouse regular `npm run type-check` takes around 10min in project Do we have a reliable way to check that LSP diagnostics are working? Prompt like > give me a list of TypeScript errors in this file. Just run `npm run type-check`. If I'm using prompts like > use LCP diagnostics to get TypeScript errors I see a response I don't have access to any LCP diagnostics ### Plugins _No response_ ### OpenCode version 1.1.49 ### Steps to reproduce 1. Create a vue file with ts error e.g. ``` <script setup lang="ts"> const test: string = 1 console.log(test) </script> <template> <div>hello</div> </template> ``` 2. Run propmpt `give me a list of TypeScript errors in this file` 3. See that response do not use LSP ### Screenshot and/or share link /status after reading Vue file <img width="892" height="531" alt="Image" src="https://github.com/user-attachments/assets/471aa81c-9050-4422-9bb3-8c0b438f65f3" /> ### Operating System Windows 11 with WSL ### Terminal bash
yindo added the windowsbug labels 2026-02-16 18:09:52 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 3, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #2756: Vue LSP not reporting diagnostics - This is specifically about Vue LSP not working properly
  • #742: LSP Diagnostics return nothing in large project - Reports LSP diagnostics returning empty results
  • #711: How to get opencode to use LSP? - General issue about LSP not being utilized

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 3, 2026): This issue might be a duplicate of existing issues. Please check: - #2756: Vue LSP not reporting diagnostics - This is specifically about Vue LSP not working properly - #742: LSP Diagnostics return nothing in large project - Reports LSP diagnostics returning empty results - #711: How to get opencode to use LSP? - General issue about LSP not being utilized Feel free to ignore if none of these address your specific case.
Author
Owner

@it-sha commented on GitHub (Feb 3, 2026):

@drevantonder Could you give some advice on how to verify that OpenCode actually detects TypeScript errors in Vue files?
It seems like you already have experience with this issue

@it-sha commented on GitHub (Feb 3, 2026): @drevantonder Could you give some advice on how to verify that OpenCode actually detects TypeScript errors in Vue files? It seems like you already have experience with this issue
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8402