HI getting Issues in prisma vscode extension
its not giving any problems but just showing red marks in vscode due to new updates of vscode extensions.....
i have two schema files working fine as per my intent befor some days now also working fine but showing those problems....
9 Replies
You decided to hold for human wisdom. We'll chime in soon! Meanwhile,
#ask-ai is there if you need a quick second opinion.Hi!
Can you please confirm if you are on the latest VS Code Prisma extension - 6.7.0?
yes
Hey, I have the same problem. The issue is that since moving the generated code outside of
node_modules (as the deprecation warning recommends) , and the generated code copies the schema (for god knows why), then the workspace detects the schema twice. The source and the copy. It doesn't know how to handle that. It's extremely frustrating.
@Nurul ?This is really strange. I wasn't able to reproduce this.
Do you still get this error when the generated client is created outside node_modules?
Yes. A simple reproduction would be to have your schema under a prisma folder and then your generated code under prisma/generated
For now, I have reverted back to not declaring an output and seeing the deprecation warning, but at least my IDE is usable.
this are error and showing in vscode
Thanks
@Nurul
generator client {
provider = "prisma-client-js"
output = "../../node_modules/@prisma-public/prisma/client"
}
For this version 6.5.0 its not giving errors
