Unreliable TypeScript error reporting
Recently I've noticed that WebStorm has got quite unreliable about highlighting or even keeping up with TypeScript errors.
Granted, we're running a large project, but of late we're (along with another team mate) have experienced:
- no errors in file
- errors may or may not appear
- if they appear, they may not be related to the real error
- when corrected, errors will not disappear
- downstream errors will not disappear
- when going to another file then coming back to the first file, all errors will disappear
- the whole thing seems really, really slow
If I open the same project in VSCode, it correctly highlights the errors.
I've fiddled around with the WebStorm TS settings, but no luck.
I have attached screenshots for both IDEs.


请先登录再写评论。
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:
npm i -g @vue/language-server
/usr/local/lib/node_modules/@vue/language-server
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:
registry...
typescript.service.node.arguments
key there (you can start typing property name to navigate to it)--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