Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Props intelisense for components inside node_modules #3537

Open
4 tasks done
noemission opened this issue Oct 6, 2022 · 0 comments
Open
4 tasks done

Props intelisense for components inside node_modules #3537

noemission opened this issue Oct 6, 2022 · 0 comments

Comments

@noemission
Copy link

noemission commented Oct 6, 2022

  • I have searched through existing issues
  • I have read through docs
  • I have read FAQ
  • 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants