JavaScript "console.log" highlighting incorrect

[wgumenyuk]

How it currently is:

How it should be:

Additional information

• Semantic highlighting is disabled
• No JavaScript highlighting extentions installed
• Still occurs with all extenstions disabled

Is anyone else experiencing this?

[tmurph21]

Same issue here.

Changing the settings to "editor.semanticHighlighting.enabled": "configuredByTheme" or true makes it worse.

[symonxdd]

Try reinstalling the theme? Under what circumstance does it not work? It works fine for me.

[wgumenyuk]

@symonxdd Reinstalling did nothing, unfortunately. What version of VS Code are you using?

[symonxdd]

I'm on 1.48.1. But now that I think about it, you probably have an extension that's messing with the JS syntax-highlighting. Try disabling / removing some. Let us know if you got it fixed.

[zyzski]

experiencing the same, even with this being the only module enabled. very similar to what happened when they added semantic highlighting

[wgumenyuk]

@symonxdd Even after a complete reinstall of VS Code (version 1.48.1) the issue still occurs. The only extenstion installed is this theme.

[symonxdd]

@wgumenyuk Can I ask where u got this screenshot from?

[wgumenyuk]

@symonxdd For this screenshot I activated semantic highlighting in the settings. This doesn't fix my issue though, as enabling this feature messes up many other highlights.

[symonxdd]

Could you give more examples of wrong highlights? Also, where did you active semantic highlighting?

[wgumenyuk]

You can activate semantic highlighting by either opening VS Code's settings (File -> Preferences -> Settings) or changing editor.semanticHighlighting.enabled inside settings.json to true.

This then leads to broken syntax highlighting mentioned here:

• TypeScript / JavaScript syntax highlighting changes after a few seconds
• February 2020 update broke typescript and javascript syntax
  • This comment mentions the broken highlighting of console.log as well

Semantic highlighting seems to be working inconsistent.
Please remember, that I don't use this feature normally and highlighting is still broken for me and the other participants regardless.

[symonxdd]

Thanks for clarifying the matter. I noticed that when opening vscode and navigating to a JS file I got the same problem as you, but not for long. It got fixed after a fraction of a second after showing the following message at the bottom of vscode:

Initializing JS/TS language features

So I looked for an extension with that name and found following enabled, built-in extensions:

• TypeScript and JavaScript Language Features &
• TypeScript Language Basics

Can you make sure you have those installed and enabled?
It's easy to find by open the extensions sidebar and searching for @Builtin type (with a small b!)

[wgumenyuk]

Yes, I have both extensions enabled, and see a Initializing JS/TS language features notification on startup as well.

[symonxdd]

Strange. What you could try next is uninstalling vscode with a program like IObit Uninstaller. Which deletes all the residual files as well, if that doesn't help, re-installing your OS will probably do the job 😂

[wgumenyuk]

Haha, thanks for your help. I'll take a look at it tomorrow. :)

[symonxdd]

Did you get it fixed? If not, since when does it not work? From the beginning?

[wgumenyuk]

This issue seems to have occured in one of the latest updates. Out of curiosity I installed VS Code on my Ubuntu (20.04.1) PC and the highlighting is still bugged, even with the same settings. I assume this is some bug with VS Code, since other themes also have the same highlighting error.

[symonxdd]

Alright! Hopefully it's fixed fast.

[wgumenyuk]

Let's hope so! I'm going to close this issue, thank you very much for your help. :)