Extensions and suggestions stopped working

[MarioSamison]

After the last update of VS Code, all of our extensions such as automatic import replacement and typescript suggestions aren't working anymore. Also VS Code runs really slow.

[guiherzog]

Several people are having the same issue. My temporary solution was to downgrade VSCode to 1.32.3.

[lewisflude]

I'm getting the same issue, was thinking it may have something to do with the version of TypeScript that the new VS Code ships with, as when I "select TypeScript version" to 3.3.333 it seems to be working more consistently. I could be wrong, however.

[MarioSamison]

Yeah I did that too, but I still wanted to flag this issue for VS Code so they can look into it

[lewisflude]

Doing an npm up caused my VS Code to go from 100% CPU usage to around 20%, and the issue is now solved for me (for now). I'll be keeping an eye out for any developments and I'll chime in if I discover any more info around the issue. I think one of the notable packages that needed upgrading was @types/styled-components. I believe this issue may be potentially related: DefinitelyTyped/DefinitelyTyped#34564.

To elaborate, I believe the issue was that I had all these @types type definitions that became outdated when VS Code updated it's internal version of TypeScript.

[eclectic-coding]

For what is worth, @ #71863.
This is happening with several extensions. I did test in Linux/Ubuntu VM and the problem doesn't "seem" to exist there. However, it was running slow but since I have not used VSC in a Virtual Machine before, the speed could have been from the VM. It was inserting the snippets properly though.

[Updy-karim]

Is this the same us this issue you guys have encountered /Seen ?
#72037

[eclectic-coding]

No, that is a different issue

[will-stone]

@lewisflude upgraded @types/styled-components to 4.1.14 and pointed VSCode to use TS 3.3.3333 and all issues are gone. Thanks all.

[jdahdah]

I can confirm that forcing VSCode (1.33.0) to use TypeScript 3.3.3333 has fixed the problems I was experiencing with the related issue r5n-labs/vscode-react-javascript-snippets#61.

[mjbvz]

Sounds like it could be #71886 but the description is too vague to tell. @MarioSamison please describe exactly what you are doing, what the expected behavior is, and what actually happens

Also test using latest VS Code insiders build

[MarioSamison]

@mjbvz changing the typescript version to the workspace typescript version fixed everything for me. It seems like the new typescript version in VS Code collides with the typescript versions in the projects we're working on.

[eclectic-coding]

@MarioSamison In my case, I did not have typescript in my project, the version supplied in VS 1.33 was causing issues. I hope this is investigated before the next release.

[mjbvz]

@MarioSamison Can you please check to see if the new VS Code 1.33.1 release also fixed the issue for you

@polishedwp Typescript tooling also powers our javascript support

[arilenz]

@mjbvz I had the same issue as @MarioSamison in 1.33.0 release. Still have the same issue in 1.33.1

[eclectic-coding]

@mjbvz The problem is better, but not entirely fixed. It works but in significantly slower than previous versions. For now, I have downgraded Typescript used by VS.

[mjbvz]

Closing as duplicate of #71863 for original poster

@arilenz @polishedwp Please open new issues