-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Groundbreaking bug upon installing #67
Comments
@jamols09 I am not a massive fan of the |
Thanks @jamols09 for creating the issue. @damisparks is correct here, I need more information to reproduce this issue. |
revert to these version till the issue is fixed "@prisma/client": "^5.22.0", "@prisma/nuxt": "^0.0.35", |
@tinegaCollins were you also experiencing this issue? Could you provide a repo to help us debug this? |
experiencing the same issue on a fresh install of nuxt v3.14.1592 Steps to reproduce:
|
Hi @jharrell , @ankur-arch Here's a repository reproducing the issue : repo link With prisma/client 5.22.0 & prisma/nuxt 0.0.35 no issues I've migrated between the two versions so you can check the differences : In this large commit, you can see all the changes that been made to the generated prisma client between the two versions : |
Just for reference, on this repo : No issues directly with npx prisma generate, but fails at npm run build / nuxt build
|
@jharrell this issue started when we updated nuxt packages, I'll try to reproduce it on a sandbox |
@jharrell can I trust you with a private repo? |
Yes, you can reach me at my Prisma email: Harrell (at) Prisma (dot) io |
same issue here |
Same |
Same issue. As a temporary solution, I downgraded @prisma/client from 6.0.1 to 5.22.0 It work for me: |
As of the moment I cannot find a way to fix the issue. When you install this module you will get
PrismaClient is not a constructor
which will cause the developer tool not to show and causes some weird behavior with Nuxt.The text was updated successfully, but these errors were encountered: