IntelliSense and code analysis is super slow and often wrong [TypeScript + React + Prisma]
As the title suggest, when writing Prisma queries or importing React components, pressing Ctrl + Space, will make IntelliJ load for up to 10 seconds, before suggesting some random options. Code analysis also takes forever to notify me, if I write some invalid code. On the other hand opening the project in VS Code, and it will instantly suggest the correct options.
My only non-bundled plugins are GraphQL and Prisma. I have tried updating to the newest version, 2024.3, increased my heap size from 4 → 6 → 8 GB, disabled inlay hints, used types from server, disabled types from server, switched to WebStorm (same problem) etc. and I'm coming to my wits end.
For now I have swapped to VS Code, as this is killing my productivity and motivation, but I much prefer IntelliJ to VS Code. So this is a desperate plea, to please help me get my IDE back.
请先登录再写评论。
We are sorry to hear about that.
From what I can tell, it appears that you have created a support ticket already. I suggest that we continue our conversation there. This community forum may not be the most suitable platform for troubleshooting performance issues, as the diagnostic data is not secure or easy to share here. Thank you for your understanding.
For anyone stumbling over this because their IDE is completely unusable: You have to downgrade to Prisma 6.1.0 and NOT have the omitApi feature enabled in Prisma.
IntelliJ completely breaking when you enable the Prisma's omitApi feature has been a long known issue but since Prisma 6.2.0 the omitApi feature has been moved from experimental to stable, thus creating the omit TypeScript types any time you do “prisma db push” which will make the TypeScript service enter an infinite loop and hog all CPU cores at 100% usage.
Unfortunately they did not repair it before Prisma moved the feature causing the issue to stable. Therefore you currently can't use IntelliJ with any projects that use an up-to-date version of Prisma.
There is currently no workaround anymore.
Hello,
In such cases, we recommend enabling the
Use types from serveroption inSettings | Languages & Frameworks | TypeScript. If this does not help, please feel free to create an issue on YouTrack and provide your IDE logs(Help | Collect Logs and Diagnostic Data) and CPU usage snapshots. Also, a sample project where the issue is reproduced would be helpful. With this information, we will be in a better position to investigate this issue.Its a problem already identify by the prisma team, https://github.com/prisma/prisma/issues/4807#issuecomment-2788572426
but i find it interesting how i can have typesafe with vscode using 12 ram but with webstorm and 12 ram i can't
The enabling Use types from server seemed so far to solve the problem for me.
Using NextJS with Prisma and had the same problem as thread starter.
I Won't agree
Same issue, nodeJS+TS
m4pro 48Gb
10Gb allowed for IDEA/WebStorm
0 external plugins.
It's not a problem with a PC or a project.
It occurs on any projects!
TS builds > 60 sec. Even code saturation takes 30+ Sec
Show/hide ts errors 60+ sec
VS code works perfect.
I’m very sorry to hear about your bad experience with the recent IDE version.
Please try profiling the issue per instructions in https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems, and share the captured snapshot along with the IDE logs (these can be collected with the Help > Collect Logs and Diagnostic Data menu action) in a new youtrack ticket so we can investigate your problem more thoroughly.
Oh my god, it really sucks. Even after a maven clean it still shows the errors and they don't go away, but the application compiles just fine.
That is so not acceptable for a professional premium IDE! WTF
And you can't trigger a refresh or a re-analyze.
Hi Joe Light, We’re sorry that you’ve had this experience.
Based on your description and the title of this forum thread, it seems that you’re encountering a different issue.
In any case, we’ll be happy to review your problem individually. Please create a new ticket using this link, provide a more detailed description of your issue, and attach the logs collected via Help | Collect Logs and Diagnostic Data. It will help us investigate your problem further.
Thank you!