You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Vetur: Restart VLS
Info
Vetur settings
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 insidenode_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 oftsconfig.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.
The text was updated successfully, but these errors were encountered: