IntelliSense not working after updating vscode to 1.64

[Sezar-SZ]

Hi, I updated the vscode to version 1.64 and now the IntelliSense doesn't work.
Syntax Highlighting seems fine but IntelliSense is not working as expected.

Screenshot

Build environment:

• VSCode Version: 1.64
• Extension Version: 1.7.2
• OS: Windows 10

Edit:
This issue is upstream from VSCode itself so either:

• Rollback to VSCode 1.63
• Use VSCode Insiders

Root cause: microsoft/vscode#142139

[cleytoo]

Same thing here, was normal yesterday. Happened right after VScode update :/

[maxleon52]

Same thing here, :/

[willian-lemann]

Same thing in here

[bsquiroz]

same issue

[Jhonatan-lezcano]

my operating system is Linux Mint 20.2 Cinnamon and it works without problems, but my colleagues with a windows 10 operating system the extension fails,the operating system may be something to consider for this issue

• current version of VSCode: 1.64.0
• Operating system: Linux Mint 20.2 Cinnamon
• technology: React with Typescript

[Sezar-SZ]

@Jhonatan-lezcano I'm using Windows 10 too. So yes, maybe that's where the problem is coming from.
I will edit the issue and add OS, so maybe it could help to solve the problem.

[Guilherme11gr]

Same issue!

[Theakayuki]

same Issue as well windows 10 started yesterday after update to 1.64, did reinstall of both the extension and vscode.

[DMCFA]

same issue with windows 10 after vscode update (1.64)

[Hugocorreaa]

i have the same issue too!

[seongminn]

same issue too with windows 10

[pzajas]

Yeap, windows 10 here too. Guess we have to wait for the fix :(.

[seokwoo-park]

same Issue, thanks for the Extension but can't wait till fix the bug :)

[sihyun92]

same issue too with windows 10 :(
I can't await to fix bugs.

[jarrisondev]

For the people that need the extension can try installing the November vscode version (1.63), here in this page it's the executable:
https://code.visualstudio.com/updates/v1_63

Maybe this could be a quickly solution.

[jasonwilliams]

Hi all thanks for the reports. Can you include your VSCode versions and windows versions please.
I'm using Windows 11 with VSCode insiders, tested this this morning and its working for me.

Can someone else try the latest VSCode insiders and report back?

Version: 1.65.0-insider (system setup)
Commit: 62de8dc3f78b8bef1eb62deeb093164a8d76c254
Date: 2022-02-04T11:47:20.200Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000

Because I can't reproduce it right now someone else will need to take a look.
The Contributing Guide goes into more than enough detail on how to look into this.

There's also a Discord chat too

[SEBIIWA]

this issuse happens pretty much every one or two update in vscode, it started with typescript managed project with NextJs and the CRA templates, now I am using a react native with styled components and other project in JS yet the problem still available, despite the extension does not behave well with typescript, I think there is a problem that runs way deep.

Version: 1.64.0 (system setup)
Commit: 5554b12acf27056905806867f251c859323ff7e9
Date: 2022-02-03T04:22:20.678Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000

PS: it behaves the same with (.js/.jsx | .ts/.tsx)

a react native with styled components project using JS

a next js project with typescript:

[Sezar-SZ]

Thank you for your response @jasonwilliams
I tried the latest VSCode insiders and the extension was ok there.
So yeah.... probably that problem was just about VSCode and it will be fixed in the next version.

Again, Thank you very much for your attention.

[SEBIIWA]

this issuse happens pretty much every one or two update in vscode, it started with typescript managed project with NextJs and the CRA templates, now I am using a react native with styled components and other project in JS yet the problem still available, despite the extension does not behave well with typescript, I think there is a problem that runs way deep.

Version: 1.64.0 (system setup) Commit: 5554b12acf27056905806867f251c859323ff7e9 Date: 2022-02-03T04:22:20.678Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.22000

PS: it behaves the same with (.js/.jsx | .ts/.tsx)

a react native with styled components project using JS

a next js project with typescript:

Revirting to vscode 1.63 update fixes the problem of the extension

[Hortigas]

For the people that need the extension can try installing the November vscode version (1.63), here in this page it's the executable: https://code.visualstudio.com/updates/v1_63

Maybe this could be a quickly solution.

worked for me

[Deknoinarak]

@jasonwilliams I have tested in VS Insider and it worked too!

OS: Windows 10
VS Code Version: 1.65.0 (Insider)

[benHung1]

For the people that need the extension can try installing the November vscode version (1.63), here in this page it's the executable: https://code.visualstudio.com/updates/v1_63

Maybe this could be a quickly solution.

worked for me

Help me a lot , Thx

[jasonwilliams]

The upstream issue seems to be this:
microsoft/vscode#142139

[hanseulhee]

In my case, It was not applied in version 1.64.0, but it was applied after changing to 1.63.2. 😀

download in this link

[leonardojacomussi]

Same problem here (and same settings too). Downgrading to VSCode version 1.63.2 worked for me.

[TheAleSch]

same issue here w11

[MD-Fleksa]

The upstream issue seems to be this: microsoft/vscode#142139

this is awesome. it works for me

[jasonwilliams]

Please don’t do “me to” messages. It alerts people watching this thread and adds noise.
If this affects you you can upvote the top comment.

i will close for now as it’s been fixed upstream.

[carloscmarcelino]

For the people that need the extension can try installing the November vscode version (1.63), here in this page it's the executable: https://code.visualstudio.com/updates/v1_63

Maybe this could be a quickly solution.

Worked for me, tks bro

[Mathews-mw]

Recently, I had this same problem

What did I do?

I turned off all my installed extensions;
Then, I turned on the styled-components extension;
So, I started to turn on one extension at a time until I found one that was causing conflict and I found.

In my case, the extension that was conflicting was 'JavaScript and TypeScript Nightly v5.0.20221112'. I'm not exactly sure why this extension causes a conflict with styled-component, but I turned it off and everything was back to normal.

Perhaps, for each case it is a different extension that causes conflict, but I think it's worth trying to check one by one.

[akshaysr-buku]

Recently, I had this same problem

What did I do?

I turned off all my installed extensions; Then, I turned on the styled-components extension; So, I started to turn on one extension at a time until I found one that was causing conflict and I found.

In my case, the extension that was conflicting was 'JavaScript and TypeScript Nightly v5.0.20221112'. I'm not exactly sure why this extension causes a conflict with styled-component, but I turned it off and everything was back to normal.

Perhaps, for each case it is a different extension that causes conflict, but I think it's worth trying to check one by one.

Thank you @Mathews-mw , Irrespective of VS code version, JavaScript and TypeScript Nightly was affecting Styled component autocomplete feature

[Mathews-mw]

Glad it helped you too.

[VincentRuoka]

Recently, I had this same problem

What did I do?

I turned off all my installed extensions; Then, I turned on the styled-components extension; So, I started to turn on one extension at a time until I found one that was causing conflict and I found.

In my case, the extension that was conflicting was 'JavaScript and TypeScript Nightly v5.0.20221112'. I'm not exactly sure why this extension causes a conflict with styled-component, but I turned it off and everything was back to normal.

Perhaps, for each case it is a different extension that causes conflict, but I think it's worth trying to check one by one.

Thanks a lot @Mathews-mw ! You just saved my sanity. I couldn't figure out why it stopped working. Can't even remember installing that extension.

[Mathews-mw]

Thanks a lot @Mathews-mw ! You just saved my sanity. I couldn't figure out why it stopped working. Can't even remember installing that extension.

Honestly, I don't even remember installing that extension too. But, glad that works to you too :)

[leoselig]

Did anyone figure out why this extension was enabled for them. I'm proper 95% certain that I did not install it since I recently did a review of my installed extensions.

[VincentRuoka]

Im pretty sure it got installed as part of some TS package I installed. Sadly I can't tell you what exactly because of this issue I cleaned up my whole VSC instance. Maybe it already was there and an update caused the bug with styled-component.
I remember that the issue started after updating VS Code to the November built.

[huajiujiang]

You can disable the related plug-ins at the beginning of typescript and js temporarily, and then enter them. Then you can start the plug-ins, which can also be used normally. I am like this

[guyeilon]

'JavaScript and TypeScript Nightly

help for me, thanks!

[Clypsonymity]

Hi, am I the only one who cannot fix this issue? aka the autocompletion css in jsx files 😅

I'm using :

react 18.2
vscode 1.63.2 as suggested
vscode-styled-components 1.7.5
.+ disabled all extensions..

[Mathews-mw]

Hi, am I the only one who cannot fix this issue? aka the autocompletion css in jsx files 😅

I'm using :

react 18.2
vscode 1.63.2 as suggested
vscode-styled-components 1.7.5
.+ disabled all extensions..

Probably, it's because your vscode version. When a trying this solution, my vscode version was 1.74. Try to update to the latest and then, tur on only the styled-components extension and see if it works to you.

[Clypsonymity]

Just tried this but without any success.. So I came back to the good old method:
Indeed, the best way was to delete everything and restart all from scratch like every times 🚀

I completely uninstalled vscode and all residual data such as extensions folders etc.. and all reinstalled from scratch and work perfectly 👌

[mateuscesarglima]

Recently, I had this same problem

What did I do?

I turned off all my installed extensions; Then, I turned on the styled-components extension; So, I started to turn on one extension at a time until I found one that was causing conflict and I found.

In my case, the extension that was conflicting was 'JavaScript and TypeScript Nightly v5.0.20221112'. I'm not exactly sure why this extension causes a conflict with styled-component, but I turned it off and everything was back to normal.

Perhaps, for each case it is a different extension that causes conflict, but I think it's worth trying to check one by one.

Thanks a lot! The extension JavaScript and TypeScript Nightly is conflicting with Styled-components ext.

it helped tooooo

[avitslv]

I'm working on typescript project using styled-components.
Can confirm, after disabling JavaScript and TypeScript Nightly extension, suggestions list works.

[jasonwilliams]

@mateuscesarglima & @avitslv your issue is not related to this thread. You need to go to #387 which is about the typescript nightly extension causing problems.

I’m going to mute this thread now as there’s just noise being added which isn’t related. If you think you have an issue, check troubleshooting first on the front page, then search other issues, and only then make a new issue.