Closed theRenard closed 4 months ago
TypeScript errors are reported by vue-tsc (which is used by the "Vue - Official" VS Code plugin aka. Volar). They have nothing to do with ESLint or eslint-plugin-vue, so they are not reported in the ESLint CLI.
Ok thank you for you quick answer!
Checklist
Tell us about your environment
Please show your full configuration:
What did you do?
I have a codebase with a mix of class components and composition api. For class components and typescript files I can see errors in both VSC and in CLI, but when using composition api I see errors only in VSC, I can write the most wrong code in my
.vue
. files without any complain from the builder. Only typescript errors are not catched, those who correspond to the plugin are catched.In class components ✅
In CLI
In typescript ✅
In composition api ❌
(there are two errors here, first is
vue/no-ref-as-operand semi
and is in both VSC and CLI and the other on which is a typescript errorthat safely passes the CLI check.
What did you expect to happen?
Catch any typescript error ever in
<script setup>
What actually happened?
Repository to reproduce this issue Can't share the whole codebase