Repository navigation
It seems like OpenCode don't see TypeScript errors in Vue files #11910
Description
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 runnpm 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
- 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>
- Run propmpt
give me a list of TypeScript errors in this file - See that response do not use LSP
Screenshot and/or share link
/status after reading Vue file
Operating System
Windows 11 with WSL
Terminal
bash
Activity
github-actions commentedon Feb 3, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
it-sha commentedon 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
github-actions commentedon Apr 5, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.