vetur icon indicating copy to clipboard operation
vetur copied to clipboard

Props intelisense for components inside node_modules

Open noemission opened this issue 2 years ago • 0 comments

  • [X] I have searched through existing issues
  • [X] I have read through docs
  • [X] I have read FAQ
  • [X] I have tried restarting VS Code or running Vetur: Restart VLS

Info

  • Platform: macOS
  • Vetur version: 0.36.0
  • VS Code version: 1.71.2

Vetur settings

"vetur.validation.templateProps": true,
"vetur.experimental.templateInterpolationService": true,

Problem

When I import a component from a package installed with yarn link Vetur correctly parses the component and offers props IntelliSense. While this package is symlinked Vetur and Vscode resolve to the actual file location. (Checked by hovering on the import statement)

On the other hand when the package is installed properly with yarn add, Vetur cannot offer any prop intelisense. In that case, Vetur and Vscode resolve the file to its location inside node_modules. (Checked by hovering on the import statement)

It seems that although Vetur can parse the component it will ignore it if its location is inside node_modules. I have already tried to add the package in the include property of tsconfig.json but without any luck.

Reproducible Case

You can reproduce the case if you try to use a component from another package while the package is properly installed and then use it when the package is symlinked.

noemission avatar Oct 06 '22 10:10 noemission