Closed mlankamp closed 1 month ago
Same problem with Quasar but only after build + type-check (vue-tsc --noEmit -p tsconfig.vitest.json --composite false)
error TS2339: Property 'dense' does not exist on type 'CreateComponentPublicInstance<Readonly<ExtractPropTypes<{}>>, { mobileTableRef: Ref<HTMLDivElement | null>; isLoadingUsers: ComputedRef<boolean>; ... 19 more ...; showDate: (time: string | null) => string; }, ... 17 more ..., {}>'.
<q-item v-for="user in users" :key="user.id" dense class="user border-radius-md column bg-secondary">
This also occurs on regular components. In our case in Nuxt 3.
The "solution "is to use :foo="true"
instead of foo
directly, but that's obviously not how it's supposed to work.
We'll skip this version until a fix is released.
I first noticed with Vuetify, but my example uses the stackblitz vue-ts template with an extra boolean prop to demonstrate the problem.
I'm also getting this issue. There is another issue that is strange as well. I have a component that looks like this:
<custom-component first-second>
Where the attribute firstSecond
is a boolean prop. This is producing 2 errors:
Property 'first' does not exist on type ...
Property 'second' does not exist on type ...
I also encountered this problem
Error is happening when I use certain Vuetify components with a v-for loop.
Ok:
Error:
vscode:![image](https://github.com/vuejs/language-tools/assets/8513556/8cdd65cd-853e-4db7-acec-068af625cdaa)
build output:
example: https://stackblitz.com/edit/vitejs-vite-weuexn?file=package.json,src%2FApp.vue&terminal=build