nuxt-property-decorator + typescript

[Zenthae]

• I have searched through existing issues
• I have read through docs
• I have read FAQ (lol there is no FAQ.md)
• I have tried restarting VS Code or running Vetur: Restart VLS

Info

• Platform: Win
• Vetur version: latest 😉 (0.31.3)
• VS Code version: latest 😉 (1.52)

Problem

there is no auto-completion / IntelliSense for props and data on custom component using nuxt-property-decorator and typescript

Reproducible Case

[yoyo930021]

I can't repro it.

[yoyo930021]

Please provide a repro case.
Please read https://github.com/vuejs/vetur/blob/master/.github/NO_REPRO_CASE.md.

[Zenthae]

i solved the case, it's because i wasn't importing my components since nuxt is doing it by default, so it probably wasn't able to find the definition. but it's sad since it mean that we cannot take advantage of this functionality. is it possible to tell Vetur to look for components directly in a folder ? and not only specifically imported ones ?

[yoyo930021]

i solved the case, it's because i wasn't importing my components since nuxt is doing it by default, so it probably wasn't able to find the definition. but it's sad since it mean that we cannot take advantage of this functionality. is it possible to tell Vetur to look for components directly in a folder ? and not only specifically imported ones ?

I am not familiar with nuxt.
but I think you only need this feature.
https://vuejs.github.io/vetur/guide/global-components.html

[Zenthae]

you're my savior ^^
if anyone get the same problem t :

module.exports = {
  projects: [
    {
      root: './',
      globalComponents: [
        // Nuxt components folder
        './components/**/*.vue',
      ],
    },
  ],
};

in vetur.config.js and you need to restart the language server or you editor ^^

[yoyo930021]

I think your problem is solved.
I close this issue.

[99linesofcode]

While it may seem that the globalComponents setting solves this issue (it might when you don't nest your components in subdirectories) it doesn't correctly solve the issue here. @nuxt/components allows you to dynamically import components from the components/ directory and any subdirectory there in. As is documented here:

https://nuxtjs.org/docs/directory-structure/components/#nested-directories

I believe this is actually a bug, possibly a very simple one to resolve for anyone familiar with the vetur code base relating to the nuxt external tag loader not being loaded correctly. See my issue for more info #3370

[SimplyCorey]

Facing the same issue with the next directories and I have not been able to find a solution.

Essentially, we have the following folder setup:

Ui/
     Button.vue

We use @nuxt/components for autoloading (per https://nuxtjs.org/docs/directory-structure/components/#nested-directories )and reference the component in our files as .

The file that vetur generates when viewing vetur doctor has these lines which does not allow vetur to pick up the UiButton component correctly.

{
  "name": "Button",
  "path": "/resources/nuxt/components/block/settings/Button.vue"
},

[jameskid007]

I've made a plugin to help jump to the corresponding component file. And nested files are supported. The name of the component is “Nuxt 2 goto". You can go to the vscode store to find it