Something about VS Code 1.4.0 has caused PowerShell IntelliSense to stop working. Must be an API change of some sort, will investigate.
Details from @tonidy:
I experienced this issue with the following environment:

With VS Code 1.3.1 the intelliSence works well. Here my log https://gist.github.com/tonidy/ed0e9a056a24ebf2a9fc02372ce2a6fe
I'm having this problem in version 1.4.0 on Windows 10 RTM Anniversary Update. The parameter names will not even auto-complete.


I have had this for a while, I thought it was something I broke! lol.
I am using the insider preview

I'm also seeing the problem in 1.4.0, looks like something changed in VS Code's completion engine. PS Editor Services is getting a completion request and returning the correct results, they're just not being displayed. Investigating...
Not sure if it helps at all, but the completions are working for actual parameter options. I.E.
New-Item -ItemT <--- Nada
New-Item -ItemType F <-- I get the menu, with File at the top of the options.
Like so:

IntelliSense behavior has indeed changed in VS Code 1.4.0 but it should be something easy to fix on my side, will give it a shot today.
@FooBartn the F for File is not a recommendation from PSES. It is completing based on it being used before.
You can tell by the ABC logo next to the name
Same problem after the latest vscode update.

Hope you can fix it soon.
BTW: Great Job with this Extension. :+1:
I'm having an issue with my IntelliSense is giving me problems as well.
Here's my version:

Whenever I hover over anything I just get "Loading...". I'm also not able to use the ctrl+D command for multiple cursors and when I try to refactor a variable in a file by pressing "F2" on it it just keeps searching and never finds anything.
I've tried closing down all instances of vs code, rebooting my computer and I'm not sure what else to do. How can I downgrade my version back to a working point?
New extension release is up with a fix for this!
@daviwil I have tried it and it's working now. Awesome :+1:
Most helpful comment
New extension release is up with a fix for this!