Unreliable TypeScript error reporting

From the screenshot it seems that the Vue language server has crashed (note the red mark on the Vue service icon in the status bar). Could you please share the logs from the language service? 

To collect service logs please go to Help | Diagnostic Tools | Debug Log Settings… and add #com.intellij.platform.lsp to the Custom Debug Configuration window.

Then restart the IDE, reproduce the issue, and send us all the IDE logs collected via Help | Collect Logs and Diagnostic Data…

I'm noticing the same thing and its making WebStorm completely unusable, writing Typescript. I can add a completely unknown token “asdfasdf” to my code and it doesnt flag it as an issue. I've downloaded VSCode which instantly flags it as an issue. I don't want to switch after using jetbrains for years but its in a completely unusable state

Taronish4 please enable verbose logging by adding #com.intellij.lang.javascript.service.JSLanguageServiceQueue:trace to the Custom Debug Log Configuration window in Help | Diagnostic Tools | Debug Log Settings… , then restart the IDE, reproduce the issue, and share your IDE’s logs (these can be collected via Help | Collect Logs and Diagnostic Data …) within a support ticket.

I'm probably not going to have the time to do that - however for posterity I downgraded my version from 2024.3.1.1 to an earlier 2024.1 and things seem to be stable now.

FWIW I seem to have gotten WebStorm to start playing ball again with Vue/TS (albeit very slowly!).

I can't say for sure which of these changes has made it work, but it is working:

• Install the Jetbrains Toolbox
• Download WebStorm EAP 2025.1
  • You may be able to use other versions or PHPStorm
• Install Vue Language Server globally
  • npm i -g @vue/language-server
• In WebStorm, go to:
  • Settings > Languages and Frameworks > TypeScript > Vue
• Point the Vue Language Server at /usr/local/lib/node_modules/@vue/language-server
  • This version is 2.2
  • 2025.1 uses 2.1.6 which also seems to work
  • 2024.3.2 uses 2.1.6
  • 2024.1.7 uses 1.8.27
• Set the settings below to "Auto" and made sure "Use types from server" is off
  • Turning it on does seem to completely break Vue/TS
  • Note that the main TS "Use types from server" is on
• I restarted my WebStorm
• Using the "Problems" panel is a good way to check if it is really working

Hey, I'd love to +1 and add that this is making webstorm completely unusable in large monorepos (e.g. for work). I can help diagnose, but I've also been having the same issues for a few weeks at least. 

Please enable verbose logging by adding #com.intellij.lang.javascript.service.JSLanguageServiceQueue:trace to the Custom Debug Log Configuration window in Help | Diagnostic Tools | Debug Log Settings… , then restart the IDE, reproduce the issue, and share your IDE’s logs (these can be collected via Help | Collect Logs and Diagnostic Data …) within a support ticket. This would help us to understand what's going on.

I created ticket https://intellij-support.jetbrains.com/hc/en-us/requests/7259491. Thanks so much!

The solution for future forum readers – my ts server was running out of memory, so I followed these instructions to increase it:

• in Help | Find action..., type registry...
• open Registry..., locate typescript.service.node.arguments key there (you can start typing property name to navigate to it)
• add --max_old_space_size option there (--max_old_space_size=4096, for example)

see https://github.com/thlorenz/v8-flags/blob/master/flags-0.11.md#max_old_space_size-0-integer
 
 

Having used Webstorm for many years, this is my anecdotal impression as well. I've had repositories where even simple Typescript error reporting around a undefined function name wouldn't show up. It feels like this started around the beginning of 2025 but since there's no apparent *crash* - it's been frustratingly inconsistent to deal with.

Please enable the debug logging per the instructions above, reproduce the issue and submit the logs in a new support ticket. This would help us to investigate it further.

Same here. Only started with latest version. Before that there was only 800% CPU usage issue, so some progress I guess. Webstorm remains completley unusable though.

 TS support in IntelliJ IDEs broke at the beginning of this year and has remained broken despite updates and clearing cache. This is a very serious issue. The project I'm working on isn't even that big

Please enable verbose logging by adding #com.intellij.lang.javascript.service.JSLanguageServiceQueue:trace to the Custom Debug Log Configuration window in Help | Diagnostic Tools | Debug Log Settings… , then restart the IDE, reproduce the issue, and share your IDE’s logs (these can be collected via Help | Collect Logs and Diagnostic Data …) within a support ticket. This would help us to understand what's going on.

Yup, same here. Something is broken, random CPU spikes to 800% and issues with correct syntax reading, unable to import components etc. The only thing that works in my case is cache invalidation to I have to make every 3-4 days or just open the project in VSC if you are frustrated enough. 

I am coding with TypeScript in IntelliJ Ultimate Edition and the inline lint errors are regularly out of sync and have been for a long time. I'd say maybe 20% of the time they are inaccurate: either they lag behind or just don't seem to make any sense. I will generate the debug logs as instructed above and submit a ticket.

Also encountered that since the switch of the TS + Angular service-powered type engine something is off. I disbaled those but it still is unbareable. Its lagging behind as everyone here described and only is fixed after a restart. This is going on for months now. If the support ticket process wouldnt be so daunting i would submit one

Same issue here after upgrading my IDE from 2023 to 2025. It's a shame we have an issue going to almost 6 months now for a product that is quite expensive. This is basic functionality on any IDE

I may have found a way to resolve these problems.
1 Close the TypeScript language server.
2 Disable the Vue language server.
I think these LSPs have some problems.
WebStorm becomes very quick after I disable these two LSPs. All highlighting, code jumping, and other abilities work well.
I don't know why, but it is what it is...

This issue has been bothering me for a long time. I suspect these two LSPs are completely broken, and at least the Vue LSP is crap. Using WebStorm's built-in support would be better. Vue's IDE support has never been good, especially in single-file components. This is very frustrating. I can hardly trust my IDE, which feels like a completely different world compared to writing Java in IntelliJ IDEA.

Same issue is happening for me in multiple React typescript projects in Intellij IDEA 2025.1.2. Intellij IDEA Ultimate typescript error highlighting is very unreliable most of the time. Works a bit after invalidating the caches and restarting, but soon after doing some changes the error reporting in the tsx components starts to be out of sync and typescript support cannot be trusted in the IDE anymore - you can only see the correct issues in the terminal by running the build. Also, after some changes in one file, you can often see the message “Analyzing” for minutes… for a small tsx file and relatively small project.

The free VSCode works and shows everything correctly and instantly.

I also see in this thread, no real support for this major issue (reported in January …) - no ETA for a fix or a workaround - just asking repeatedly for logs.

Seems very strange that such a major typescript related issue is allowed to exist for such a long time - when considering the level of reliability I got used to by the same product in the java / git world.
 

Unfortunately we can’t investigate this problem without a diagnostic data from your side. Please share the service logs in anew youtrack ticket as requested above.

I began experiencing this issue late in 2025 and it just seemed to get worse every day. Typescript and Angular template errors wouldn't get marked in the IDE or would take a long time to get marked. I eventually figured out that restarting the Angular Typescript language service temporarily fixed the issue but this fix would only work for a few minutes. After searching the forums, I found this thread and the response by samyok appears to have resolved the issue for me. I followed his instructions to change the memory settings for the language service and the issue appears to have gone away. Typescript and Angular template errors are now showing up almost immediately and I don't have to keep restarting the language service.

IDE highlights TS errors that do not exist yet fails to highlight actual type errors that can fail the build, I really have to use cursor or vscode just to be more typesafe? come on! Last two years IDE has been nothing but disappointment, unusable, especially in monorepos, I loved webstorm so much, but come on, how many more chances I should give…

I’m very sorry to hear about your bad experience with WebStorm.

Please enable verbose logging by adding com.intellij.platform.lsp to the Custom Debug Log Configuration window in Help | Diagnostic Tools | Debug Log Settings… , then restart the IDE, reproduce the issue, and share your IDE’s logs (these can be collected via Help | Collect Logs and Diagnostic Data …) within a support ticket. This would help us to investigate the issue.