Intellisense not recognizing Vue SFC's component

[lanyizi]

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

Info

• Platform: Windows
• Vetur version: 0.22.6, installed through VSIX from VSCode in administrator mode
• VS Code version: 1.39.2 (System setup)

Problem

Looks like VSCode won't recognize my Vue component in the SFC file, but just an ordinary object:

When I write this., computed properties predefinedTags, computedTags etc. are suggested as methods because like mode, they are all declared as computed's member, but I can't get any intellisense suggestions from data().

Output from Vue Language Server log:

Loaded bundled typescript@3.6.3.
Vetur initialized

[Soresu]

I've just noticed the same thing. I've checked it in the previous verisons, it stopped working after version 0.22.2.

[octref]

<template>
  <div></div>
</template>

<script>
export default {
  data() {
    return {
      tags: ['CMS']
    }
  },
  computed: {
    mode() {
      this.
    }
  }

};
</script>

Please provide a minimal reproducible case.

[Soresu]

@octref Currently with Vetur 0.23.0 and VSCode 1.42.0 it is working fine. Although in the template tag, the nested properties are not visible.

It knows that there is an obj variable with test and test2 properties, but there is no intellisense after the dot. Also there is no info about the Vue instance properties, like $router. It is visible in the script tag.

[octref]

@Soresu That's a different issue, tracked in #1129.

[Soresu]

@octref Ah fine, thanks for the info.
Meanwhile, the issue happened again. When you define the "props" property on the Vue instance and you return a property from a computed, the intellisense stop working in computed fields. And in the tooltip, it is labeled as method instead of property.

Without "props" property (or returning a local variable), it is working, which is interesting.

[octref]

Can you create a minimal repro by forking https://github.com/octref/veturpack and open a new issue?

[yoyo930021]

If vetur.useWorkspaceDependencies: true,
you will use typescript@2.9.2 in vetur and not have any error.
The error is happened when using typescript@^3.x.x.
It's a type definition error in Vue lib.
Ref: vuejs/vue#11235

[octref]

@yoyo930021 Thanks a lot for finding the issue and providing a fix!
I'll mark this as upstream and close it then.

[ZhengXiaowei]

why dosen't it work for me?