When project has jsconfig.json with path alias, ".vue" intellisense is slow
See original GitHub issueInfo
- Platform: win
- Vetur version: 0.21.0
- VS Code version: 1.34.0
Problem
when project with jsconfig.json
has path alias, .vue
intellisense is slow, *.js
normal.
{
"compilerOptions": {
"baseUrl": ".",
"paths": {
"@/*": ["./src/@/*"],
...other 5 path maps,
"$public/*": ["./src/$public/*"]
}
},
"exclude": [
"node_modules"
]
}
Reproducible Case
.vue
.js
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:7 (2 by maintainers)
Top Results From Across the Web
When project has jsconfig.json with path alias, ".vue ...
I setup path-mappings a few days ago. Since then, Vetur is really slow. It seems like Vetur is having a queue with file-states...
Read more >VSCode Intellisense does not work with webpack + alias
Try creating a jsconfig.json and configuring the paths compiler options { "compilerOptions": { "baseUrl": ".", "module": "commonjs" ...
Read more >Use jsconfig.json to improve VS Code IntelliSense on a Vue.js ...
It can be done by adding a jsconfig. json file in your project. In this file you will specify a mapping table to...
Read more >FAQ | Vetur - GitHub Pages
json , jsconfig.json in your project, Vetur will use fallback settings. Some features such as including path alias, decorator, and import json won't...
Read more >tsconfig.json path aliases not resolved in .vue files : WEB-38843
Is there work in progress for this bug? It's really one of the last problem appearing when using Vue + Typescript, and resolving...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have the same situation using TypeScript with my
tsconfig.json
. It seems like the more aliases I have, the slower it gets.I setup path-mappings a few days ago. Since then, Vetur is really slow.
It seems like Vetur is having a queue with file-states to analyze: If i start typing something like
long_word
, i can often see errors like:'lon' is unknown
'long_' is unknown
( a few seconds later)'long_wor' is unknown
(more seconds later)I’ll create a reproduction repository in the next few days.