VsCode February 2020 (version 1.43) update broke syntax highlighting
See original GitHub issuehttps://github.com/microsoft/vscode/issues/92308
I tested on JS only but I read other languages are affected as well.
Temporary fix is to add
"editor.semanticHighlighting.enabled": false
in settings.
With semantic highlighting enabled:
disabled:
Issue Analytics
- State:
- Created 4 years ago
- Reactions:20
- Comments:13 (6 by maintainers)
Top Results From Across the Web
February 2020 (version 1.43) - Visual Studio Code
Whitespace characters will now be rendered on highlighted text by default. Here the tab and space whitespace characters are displayed in the selected...
Read more >TypeScript / JavaScript syntax highlighting changes after a few ...
I just updated and my javascript syntax highlighting broke. VSCode Version: 1.43; OS Version: Windows 10. Does this issue occur when all ...
Read more >Visual Studio Code syntax highlighting is not working for ...
This was causing the syntax highlighting for .js and .ts files (.jsx and ... This extension has now been updated and this issue...
Read more >Visual Studio Code(VSCode) 1.43 高亮問題 - 是Ray 不是Array
Enable JS/TS language features change the assets of VS Code · February 2020 (version 1.43) update broke js syntax highlighting ...
Read more >Chocolatey Software | Visual Studio Code 1.43.2
Meet IntelliSense: Go beyond syntax highlighting and autocomplete with IntelliSense, which provides smart completions based on variable types, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
will adapt that in next version, but need some time, so you guy can set it be false, and watiting next version
@PandawanFr I think it’s not necessary, and I just try to adapt that and found that will make some breaking change