-
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
Incompatibility with Prisma ORM 6 #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: |
Same issue. Sigh. |
Hi @gsxdsm if you downgrade to Prisma Client |
Will try, but I'd like to be on 6.1. Not sure why nuxt-prisma is stuck on an older version of Prisma. Doesn't make sense. |
Prisma 6 is only 3 weeks old, so I guess we need to be patient and give a break to opensource maintainers that already give a lot to the community. |
Had the same issue on a fresh Nuxt 3 install. Downgrading solved it. Thanks for all your efforts towards the project! "@prisma/nuxt": "^0.1.3", |
sam issue, downgrade works fine |
Thanks for the patience on this everyone 🙏 . I can't reproduce the error with Just be sure to use the required node versions required for Prisma 6 too. |
Another data point: problem occurred with 6.1.0. I realised I had installed it using node 22.2.0, so I updated to node 22.12.0 and did a clean reinstall. Problem still occurred. Downgraded to Prisma 5.22.0 as described above and the problem disappeared. |
@goldengecko 👋 , can you check if this is resolved in the pre-release version? The package wasn't published as there weren't significant changes 😕 from the PR above. |
@ankur-arch Yes, I can confirm that it works with the following settings in node 22.12.0:
though I do get some errors about missing fonts in the Prisma Studio instance it boots up: GET http://localhost:5555/inter-latin-400-normal.27ae72da.woff2 net::ERR_ABORTED 404 (Not Found)Understand this errorAI GET http://localhost:5555/inter-all-400-normal.4c1f8a0d.woff 404 (Not Found)Understand this errorAI GET http://localhost:5555/inter-latin-600-normal.87d718a2.woff2 net::ERR_ABORTED 404 (Not Found)Understand this errorAI GET http://localhost:5555/jetbrains-mono-latin-400-normal.80a5dc9e.woff2 net::ERR_ABORTED 404 (Not Found)Understand this errorAI GET http://localhost:5555/inter-all-600-normal.d0a7c8a9.woff net::ERR_ABORTED 404 (Not Found)Understand this errorAI GET http://localhost:5555/jetbrains-mono-all-400-normal.f86807b7.woff net::ERR_ABORTED 404 (Not Found) Thanks for getting this working |
🎉 This issue has been resolved in version 0.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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: