WebStorm issue - not recognizing Prisma client regeneration?
Hi everyone, I am working with Prisma via WebStorm on a TypeScript project. My main issue at the moment is that whenever I run
npx prisma generate, it seems I have to restart my IDE for WebStorm to actually notice that the model has been regenerated and index the changes. Does anyone know of a workaround?12 Replies
Hello @Cold 👋
Prisma Webstorm extension is managed by the Webstorm team. I'll search if anyone else has reported this same issue.
Does this happen on latest version of Prisma and Webstorm IDE?
I have the same problem with Jetbrains. The solution is to put the output folders out of the node_modules
Yep
Surely this is not the only solution? This seems like a workaround that just creates unnecessary changes to .gitignore amongst other things
No, Webstorm etc. reindex the node_modules folder only after an install or program start
i hate it too, but i prefer intellij to vscode so i live with it
How do I reindex that folder?
Oh nvm
I see what you're saying
This honestly makes me tempted to give Fleet another go at this point
sorry for my english
No probs
i dont know if it works in fleet
I believe Prisma has a plugin for Fleet let me double check
nope
They don't? Shoot
currently there is none yet