Vetur is not reading Vuetify type definition files from the right place

• I have searched through existing issues
• I have read through docs
• I have read FAQ

Info

• Platform: Linux
• Vetur version: 0.22.0
• VS Code version: 1.37.0

Problem

Vetur is unable to read Vuetify type definition files alacarte.d.ts, colors.d.ts, index.d.ts and lib.d.ts from their current location (node_modules/vuetify/types). Instead, it’s trying to read them from node_modules/vuetify/lib.

If I copy/symlink manually these files to node_modules/vuetify/lib, Vetur read them as expected, but vue-cli fails to build my project.

[nekosaur]

@octref this can be closed. It’s unrelated to vetur.

[patarapolw]

It seems to be relate to Vetur in that Vetur does not read tsconfig.json in the right place, when it is modified.

Also a bug on Vuetify part – https://github.com/vuetifyjs/vuetify/issues/3943

Currently, after tsconfig.json correction, there is this.$vuetify in main.ts, but not in App.vue.

Got a solution by modifying shims-vue.d.ts;

// declare module '*.vue' {
//   import Vue from 'vue'
//   export default Vue
// }

declare module '*.vue' {
  import  "vuetify"
}