vetur-yarn-workspace-typescript-definition-problem

[mariusheine]

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

Info

• Platform: Win
• Vetur version: 0.23.0
• VS Code version: 1.42.0
• Typescript: 3.7.5

Problem

When i use yarn workspaces and import something from inside the script tag of a sfc vue component and i want to go to the definition of the import i get to the *.d.ts file in the dist folder. But when i import the same thing in a "normal" file e.g. main.ts and go to definition i get to the .ts file in the src folder.

In the mouseover the resolved path for the imported module is the same in both cases so i think the differences is that in the second case it follows the sourceMappingURL and in the first one not

Reproducible Case

Clone this repo https://github.com/mariusheine/vetur-yarn-workspace-typescript-definition-problem and follow the README.

Then open App.vue and main.ts and try "Go To Definition of any import of @vetur-yarn-workspace-typescript-definition-problem/domain.

[yshrsmz]

Maybe it's not 100% the same issue, but I'm also seeing an issue regarding yarn workspaces and typescript.

In my case, Vetur does not respect types configured in a tsconfig in a workspace.

For example, I'm using Nuxt in one of the workspaces and added @nuxt/types like below.

// packages/workspace-a/tsconfig.json
{
  "compilerOptions": {
    "types": "types": ["@types/node", "@nuxt/types"]
  }
}

(only this workspace-a has a dependency to Nuxt)

But Vetur seems to not recognize this and show warnings when I try to use methods added by @nuxt/types, such as asyncData

btw it does compile successfully

[yshrsmz]

Whoops, looks like my real issue is #815

[heavenkiller2018]

any updates?