You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vuetify Version: 3.7.1 Last working version: 3.7.1 Vue Version: 3.5.6
Steps to reproduce
clone repo
run npx vue-tsc --noEmit
Expected Behavior
This should not fail and used to work in vue ~3.4.0
Actual Behavior
This fails with: Default export of the module has or is using private name 'FilterPropsOptions'. and Default export of the module has or is using private name 'ThemeInstance'
In a way larger project, we require the use of declarations. Furthermore, do to deployment schemes, we do not use the unplugin-vue-components/vite in our vite configuraion, and thus require an import of the veutify components.
If used with defineComponents syntax, which almost all of our code base is, this will throw the above mentionend TS error as of vue ^3.5.0. This seems to work as expected using a setup script.
I hit this with something as simple as just using VForm on the type of the the submit event callback, it seems that we have an un-exported SubmitEventPromise in vuetify/lib/components/index.d.mts, and an exported one in vuetify, which is indeed wrong and is what causing this error. This is likely coupled with some change in the Vue template compiler that was done at some point which then triggers this error.
Environment
Vuetify Version: 3.7.1
Last working version: 3.7.1
Vue Version: 3.5.6
Steps to reproduce
npx vue-tsc --noEmit
Expected Behavior
This should not fail and used to work in vue ~3.4.0
Actual Behavior
This fails with:
Default export of the module has or is using private name 'FilterPropsOptions'.
andDefault export of the module has or is using private name 'ThemeInstance'
Reproduction Link
https://github.com/bkuster/vuetify-typedeclaration
Other comments
In a way larger project, we require the use of declarations. Furthermore, do to deployment schemes, we do not use the
unplugin-vue-components/vite
in our vite configuraion, and thus require an import of the veutify components.If used with
defineComponents
syntax, which almost all of our code base is, this will throw the above mentionend TS error as of vue ^3.5.0. This seems to work as expected using a setup script.This may be related to this: vuejs/language-tools#1232?
The text was updated successfully, but these errors were encountered: