Ray

> I think the [deletion here](https://github.com/vuejs/language-tools/pull/4492/files#diff-1d432278152c845126fa9e323391375cf8fa8806a2cad5c1da6282dae4019947L15) caused this issue. The configuration I used below can solve some problems, but the props check failed. > > ```json > "vueCompilerOptions": { >...

Could you please provide a reproduction without using vuetify's types? Thanks in advance.

Sorry I don't mean that. I mean you can copy and simplify vuetify's types and inline them to this SFC. Anyway I'll debug locally.

Blocked by https://github.com/vuejs/core/pull/9556 because currently we are unable to extract the original component definition

Could you please check: https://github.com/fi3ework/vite-plugin-checker/pull/327, https://github.com/fi3ework/vite-plugin-checker/blob/main/packages/vite-plugin-checker/src/checkers/vueTsc/main.ts? I thought they might be helpful.

Perhaps no? I'm not familiar with volar.js but I guess you may use `proxyCreateProgram` and `getLanguagePlugins` together?

This should not affect auto complete, error reporting etc since it is just a display issue

@LinusBorg Could you please transfer this issue to vuejs/language-tools? Thanks

https://github.com/vuejs/core/blob/93324b2ec06b26662b77abc2a75d21ecbe8913db/packages/compiler-core/src/transforms/vIf.ts#L206-L216 A `` with v-if will be turned into an `IF_BRANCH` node, we should handle it in https://github.com/vuejs/language-tools/blob/master/packages/language-core/lib/codegen/template/elementDirectives.ts.

Should be fixed by https://github.com/vuejs/language-tools/commit/cb540323d4f0e80feed4feb4fea301f7d532f0c5? Do you mean there is no type checking?