Open chrmarti opened 7 years ago
From @ramya-rao-a on April 2, 2017 19:53
For which language are you finding intellisense slow?
From @hengkx on April 3, 2017 2:56
@ramya-rao-a js code intellisense Very slow,use https://github.com/airtoxin/Electron-React-Boilerplate
From @aeschli on April 3, 2017 7:33
@hengkx Can you attach a code sample that shows the slowness?
From @hengkx on April 3, 2017 7:54
@aeschli custome js code intellisense example "dg": { "prefix": "dg", "body": [ "document.getElementById($1)" ], "description": "document.getElementById(id)" },
small project is normal intellisense ,large project shows slowness
From @aeschli on April 3, 2017 10:59
Sorry, you have to give more precise steps to show what you are doing and what is slow. Also screenshots or an animated gif can be helpful.
From @hengkx on April 4, 2017 6:56
@aeschli
From @aeschli on April 4, 2017 7:21
@hengkx Thanks!
Can you run without any extension and see if that makes a difference?
Start code with code --disable-extensions
From @hengkx on April 4, 2017 13:17
@aeschli Thanks, This flow-for-vscode flowtype 0.5.0 disable, code intellisense speed normal
confirm
Same here, I can barely use flow
me too man!
I moved away from Flow and I'm using TypeScript now, much much better. Super fast, automatic imports, code completion, smart variable completion depending on type. It's almost become an IDE!
I am experiencing the same issue. It's really really slow on Windows. I have colleagues sitting next to me on a Mac and on Ubuntu and they're fine (well about as fast as flow gets I guess, still nowhere near the blazing fast speed of typescript). Why is it so slow on Windows?
Has anyone still got this issue with v0.67.0?
I have given up on what seemed to be a fantastic addition to my JS code and a credible alternative to TS. Will check again in a few months :)
I've been doing some work in jest with flow + vscode using the technique in https://github.com/flowtype/flow-for-vscode/issues/211 and it worked well
@orta are you on windows?
Nope, ah this is a windows issue - I don't think this issue should be on the vscode extension at all, seems like a problem with flow itself.
You're probably right
Same issue. Very slow on windows 10, even with a good computer. I tried disabling the builting typescript & javascript but then autocomplete stopped working.
have any other windows users tried this language server extension? It seems to be faster than the other flow extensions (still not as fast as on a Mac).
UPDATE - You can use "flow.useLSP": true
instead!
@rssfrncs have you tried setting up "useLSP": true
in your config? It uses the same language server under the hood.
@thymikee just saw that thanks!
The same problem for me on Mac. Rebooting VSCode time from time helps, but this experience is so awful. I'm also working on another project In parallel with React and Typescript and TS works like a charm!
Necrobumping this issue 2 years later, not sure if same issue, already disabled vscode built-in javascript and typescript extensions, tried enabling and disabling LSP, adding more things to ignore, removing [lib] section from the config, nothing seems to work the autocomplete speed is absolutely abysmal (several seconds)
https://user-images.githubusercontent.com/1809521/129070411-1317e38d-869f-480a-ac31-d48b92a224b0.mp4
Windows 11 here, NVMe SSD. Mostly vanilla react-native repo (npx react-native init ReactNativeProj
)
@samuelhnrq same here. Flowtype is just unusable on Windows even given the latest version 0.162.1. I ended up running vscode server in WSL2, and this saved my day! Now flowtype is blazing fast as it should be. Just make sure your repo is on Linux native file system (in /home) and not in /mnt/C/...
@DimaLapshyn I cannot even run a flow-server in vscode as the extension crashes every minute or so and then bricks my hard drive re-parsing all the files.
Do you think there would be benefit of running a flow app in WSL2 even without running the extension other than speeding up flow check
(something my project needs to run)?
@Athelian from what I recall, flow check
is usable on Windows if run interactively from the command line.
@DimaLapshyn I tried both in WSL2 and on a full Linux dist, the difference is amazing! Intellisense is lightning fast and what was before a 5-10 minute flow check time is now under 30 seconds. Thank you so much.
+1
+1
Can confirm in 2023 flow on windows stand alone is still very slow and only retriggers rechecks upon saving. Through with WSL works like a charm and just as fast as MacOS
From @hengkx on April 2, 2017 14:36
Steps to Reproduce:
1. 2.
Copied from original issue: Microsoft/vscode#23818