React, Typescript syntax highlighting is not after enabling JavaScript and TypeScript Nightly extension
See original GitHub issueHi,
I upgraded my VS Code version to latest “1.73.1”
After upgrading vscode, I noticed my syntax highlighting is not working.
But, the syntax highlighting is working when I disable or uninstall JavaScript and TypeScript Nightly
extension.
System: MAC M2 OS: macOS Monterey
Syxtax highlight when the extension is enabled

Syntax highlight when the extension is disabled / uninstalled

Please let me know if there any workaround or fix ?
Thank you
Issue Analytics
- State:
- Created 10 months ago
- Reactions:13
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Latest version (5.0.221116) breaks syntax highlighting #43
React, Typescript syntax highlighting is not after enabling JavaScript and TypeScript Nightly extension #48. Open. Take colors aways #46.
Read more >Visual Studio Code syntax highlighting is not working for ...
I think this was caused by the extension called JavaScript and TypeScript Nightly. This was causing the syntax highlighting for .js and .ts ......
Read more >Javascript syntax highlighting it not working
For me it starts to work when "Enable the new JavaScript language service" (Options->Text Editor->JavaScript/TypeScript->Language Service) is set to ...
Read more >Documentation - JSX - TypeScript
JSX is an embeddable XML-like syntax. It is meant to be transformed into valid JavaScript, though the semantics of that transformation are ...
Read more >TypeScript | WebStorm Documentation - JetBrains
WebStorm supports developing, running, and debugging TypeScript source code. WebStorm recognizes .ts and .tsx files and provides full range ...
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
Downgrading the version to the previous one works for me.
I have been having this problem as well, fairly recent, only started to occur today. Had to disable the extension