Typescript inspections sometimes unreliable and/or slow

There are times when TS inspections are slow -- meaning when I fix an error, WS can take several seconds or even longer to clear the error.

Other times, it seems like it never wants to clear the error.  I have to delete the code I just typed, type it again, then WS is satisfied.

Still other times, there are false positives -- WS doesn't report a TS error when it should have.

Has anyone else noticed this?  Is this a WS or TS issue?

41 comments
Comment actions Permalink

please create a support ticket, providing CPU snapshots taken when the issue occurs (https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems), `package.json` and `tsconfig.*.json` file(s)

0
Comment actions Permalink

2018.3 still slow as hell in angular project.

 

Usually stuck when formatting html template (Ctrl+Alt+L)

0
Comment actions Permalink

@Sasha Kalmikov please create a support ticket, attaching your log folder zipped to it

0
Comment actions Permalink

 @Elena Pogorelova Is there a support ticket we can track? This issue impacting our workflow and I'd love to see when it gets resolved.

0
Comment actions Permalink

@Jeremy no; plus the issues reported by others are not necessary _your_ issue.

please create a support ticket, providing the detailed problem description along with CPU snapshots and your log folder zipped

 

0
Comment actions Permalink

I too am encountering this issue.  But it happens when someone else on the team has edited the file with VS code.  They are on Windows VS code, I'm on a Mac wit Webstorm 2019.1

0
Comment actions Permalink

Typechecking intellisense is still pretty slow for me too, but I think performance depends on the Typescript Language Service, which I believe is maintained by Microsoft and not Jetbrains. There might not be much for Jetbrains to optimize here :(

0
Comment actions Permalink

Nathan/Jeremy,
Neither of your hypothesis explain why the valid code is marked as an error after being edited by VS Code. Hence the slow/unreliable description.

0
Comment actions Permalink

Also we are facing massive sloweness in Intellij and our Angular project.

0
Comment actions Permalink

For me I must restart the app the inspector can work otherwise it will not work...

It's so silly

0
Comment actions Permalink

Still unalterable slow on Webstorm 2022.1.3. Not the beefiest machine, and we use some of complex typescript features - but the codebase isn't huge. I appreciate that at some point you just have to throw more power at the problem or refactor the code to easier for the typescript service to analyze, but some diagnostic tips would be great. eg.: if webstorm detects that inspection result from the typesscript service is slow, it could ask to run some diagnostics. *Some* tooling for this surely exist?

https://github.com/microsoft/TypeScript/wiki/Performance

0

Please sign in to leave a comment.