Intellisense in latest Vetur is painfully slow
See original GitHub issueInfo
- Platform: macOS
- Vetur version: 0.26.1
- VS Code version: 1.48.0
Problem
Intellisense, e.g. when typing import whatever from './'
i takes around 10 seconds for suggestion to pop up.
I’ve tried downgrading VS Code to no avail. The only thing that seems to work is downgrading Vetur to 0.25.0.
Reproducible Case
- Use latest Vetur on latest VS Code. Use something like Path Intellisense (doesn’t matter) and try to import something by typing
import whatever from './'
. - Expected result: Intellisense suggestion pops up right away.
- Actual result: After 10 seconds or so intellisense suggestion pops up.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:10 (7 by maintainers)
Top Results From Across the Web
VS Code Intellisense is extremely slow - Stack Overflow
In my case, I was using the latest vs code version of v1.69 and it was very slow (~30 second delay on intellisense)....
Read more >Intellisense too slow - bad auto completion results
A fix for this issue is now available in preview release. Try out the fix by installing the most recent preview from https://visualstudio.microsoft.com/vs/ ......
Read more >Vetur Intellisense slow and incomplete if project has jsconfig
Coming soon: A brand new website interface for an even better experience!
Read more >FAQ | Vetur - GitHub Pages
Sometimes new releases have bugs that you want to avoid. Here's an easy way to downgrade Vetur to a working version: Set "extensions....
Read more >vuejs/vetur (Raised $789.00) - Issuehunt
Intellisense in latest Vetur is painfully slow. Unfunded#2163created bykjeksfjes. $0.00. Prop diagnostics not displayed for PascalCase components in ...
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
Having similar issue but with TypeScript intellisense of instance properties in <script> or <template> tags.
What I did to reproduce:
v-text="displayOptionHeader."
(notice dot at end) in some random tagThe CPU profile itself (zipped): covid-19-ctrl-space-in-template.zip Vetur 26.1, vscode 1.48.0-insider
I mainly experience it at work in a vue-property-decorator TS project but I don’t wanna share the profile from there
I had the same issue, I’m using this boilerplate for my project with compositon api https://github.com/sapphi-red/vite-boilerplate-plus. on my other project I use vue class component and not experiencing any issue