-
-
Notifications
You must be signed in to change notification settings - Fork 594
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
Vetur Intellisense slow and incomplete if project has jsconfig #547
Comments
I cannot reproduce this. Though at first load, I can feel some delay. This is caused by automatic typing resolution in vscode: vscode will automatically install typing file used in your project. After initial loading, I cannot feel significant delay. |
How long does this take for you ?
Le jeu. 16 nov. 2017 à 07:48, Herrington Darkholme <notifications@github.com>
a écrit :
… I cannot reproduce this. Though at first load, I can feel some delay.
This is caused by automatic typing resolution in vscode: vscode will
automatically install typing file used in your project. After initial
loading, I cannot feel significant delay.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#547 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACqyfMjv5F0M7matNLlxpthVDP4N12Bbks5s29qegaJpZM4QfChO>
.
|
About 3 seconds. |
And do you have complete Intellisense with props, computed, methods, and Vue API inside the component? |
Did you try on Windows 10? |
Nope, I'm on MBP. @octref do you have windows box ? |
I tested on a MBP, I cannot reproduce the slowness, but I can reproduce the incompleteness. For example, in the
|
I do have a Windows machine at home. I can try it later today. I'll take a look at the incomplete IntelliSense. |
Any update on the incomplete IntelliSense issue? |
I have the same problem , any update on this issue ? |
Can you try intelisense in JS file or TS file? Vetur shares the same TypeScript engine with VSCode. So the problem should also occur there. |
Have same issue.
The config // tsconfig.json
"include": [
"./Scripts/**/*",
"./components/**/*",
"./src/**/*"
], |
Please do provide a reproduction repo if you have the same issue. |
@octref Did you have time to check the reproduction on Windows to see if you have the issue? |
@Akryum I tested on a Windows VM running in Parallel. I do feel some lagginess in the beginning, but after a while the completion becomes smooth. What's your machine's spec? Meanwhile I tested the project on both macOS / Win, interestingly, the incomplete completion only happens on Windows...Looking into it. |
Windows 10 Pro 64-bit |
@octref I was able to reproduce this issue with a couple files in this repository. I managed to find two cases that neither intellisense or path suggestions works. I hope this information can help somehow. Specs that I used to reproduce the issueWindows 10 Open folder has a subfolder with a
|
updated 2018-5-8 ======================================= for the slow problem, I try to run simple profile. after profiling by devtool, I found that large project with the the profile |
same intellisense slow issue with jsconfig.json |
same intellisense slow issue delay about 3 seconds... |
Can you try this thing now:
|
Having the same trouble, as I write intellisence takes a couple of seconds (about 3) to say something (error, autocomplete, etc), and as I'm writing, it starts to give the intellisence response from the previous text. So it seems to send at each key that I press, instead of maybe wait for me to stop writing or something. I've enabled the verbose output, it printed like a LOT of text, how should I share here? I mean, it's really a LOT to paste in here. |
@uriannrima if more than hundreds line of the output, provide a file for download would be better, i think. |
@Akryum Does this still happen to you? |
Had same issue. Regular .js files were fine, but not .vue files. Fixed it by adding "include" in jsconfig.json:
|
I experience the same behaviour, but I've noticed something strange: I've got two projects with the same jsconfig.json, quite the same folder structure, but intellisense is very slow on one, and fast as hell on the other. {
"compilerOptions": {
"baseUrl": ".",
"module": "es6",
"paths": {
"@/*": ["*", "./src/*"],
"@static/*": ["*", "./static/*"],
},
"moduleResolution": "node"
},
"include": [
"./src/**/*"
],
} I've noticed in the Vetur logs that the task "textDocument/completion" took 158ms for the "fast" project, and 4904ms for the "slow" project. Both are quite small projects, but I can't share them, sorry. |
Changing |
@tartinesKiller That's because we are using the TypeScript language service that turns on/off features based on the |
@tartinesKiller Changing the module resolution to Can you also try another build? See #913 (comment). Thanks in advance. |
Same slowness here on my notebook. (about 3 secs) Both path suggestion and intellisense work but are slow. System info
Specs
Here's my {
"compilerOptions": {
"baseUrl": ".",
"paths": {
"@/*": [ "./src/*" ]
}
}
} After I rename it to But with the same jsconfig.json, I cannot reproduce the slowness in a minimal project yet. |
@momocow Thanks a lot for the info! If you remove |
No, almost the same. |
@momocow how about just remove the I have found that it will make vetur anylasis all files in the |
@Hanruis My project is not that big, containing 10 BTW, a good news is that after auto-updating vetur from {
"compilerOptions": {
"baseUrl": ".",
"paths": {
"@/*": [ "./src/*" ]
}
},
"include": [
"src"
]
} |
Setting |
@octref here's a somewhat abbreviated output from the verbose log (I removed some of the response bodies, or parts of large response bodies). You can see the responses often take 2-3+ seconds. The responses from the typescript server on the same computer take 75 to 250 ms generally.
|
No Intellisene for me in Vue files, but in js files. After replacing the
|
I'm encountering the same problem with the emmet auto suggestion on all my SFC. In my case it looks to be cause by the size of my project. Everything works fine when i load those components in a separate vscode window. Removing my |
me too, |
Can confirm 2-second delay for suggestions on my 2017 MBP using jsconfig in my project (containing about 500 .vue/.js files). The jsconfig file doesn't even need to contain anything. An empty jsconfig (or one containing an empty object) triggers the delay as well. |
This should be fixed in 0.20.0. A small summary:
New way it works:
|
But if |
I have this problem, too. |
我在 vue2中没有这个问题,vue3中很严重,大概有2~3s 的延迟 |
How to solve this problem |
in root folder create file vetur.config.js module.exports = { |
Info
Problem
Vetur shows incomplete Intellisense and it takes too much time.
It works fine if the project is virtual (no jsconfig or tsconfig).
Reproducible Case
https://github.com/Akryum/devfest-nantes-2017/tree/vs-code/app
Open this folder in VS Code and try Vetur in a
.vue
file.The text was updated successfully, but these errors were encountered: