-
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
Nuxt 0.1.0 issues with d.ts files #61
Comments
Thanks for reporting @husayt! I'll look into it! |
Hi @husayt, I appreciate your patience and apologize for the long wait. I’ve picked this up again and wanted to clarify: when exactly does this issue occur? Also, which package manager are you using? |
@ankur-arch I can jump in here since I have the same issue. I scaffolded a nuxt project using the latest versions a few days ago, see below my deps (removed nuxt-prisma in the meantime but also used 0.1.0) I'm using pnpm and this occurs when I run
|
@ul8 this module doesn't work with pnpm ( PR #30 should fix it, bot for some reason being ignored). So I use npm. But only 0.0.35 works, and only dev. So I can't build a working solution with any version of this module. I just tried
This might be related to windows, but again there is another pr #37 waiting for some reason. @ankur-arch there are PRs from community still open on issues affecting a lot of us, perhaps they are the key to this and other problems as well. To be honest getting @prisma and @prisma/nuxt to build and deploy (locally, firebase, cloudflare) are so much pain I already moved most of my projects to drizzle and it just works there without any drama. These issues are not difficult to resolve, but they have been out there for so long, I lost my confidence in Prisma being the reliable solution moving forward. |
In my case, the error comes when using sidebase/nuxt-auth and prisma/nuxt in the modules. But if im commented out the sidebase/nuxt-auth plugin, there is no error. |
Same issue. Using Nuxt/ui also breaks now with prisma |
Same Issue. Both side/nuxt-auth and atinux/nuxt-auth-utils will cause this problem. Just add these modules to the project and |
For me it was now fixed by simply installing the prisma and @prisma/client packages, and creating a prismaClient instance manually. |
I couldn't reproduce the exact error, but this resolves the issue and allows the project to run. It seems npm is failing to properly install and set up Prisma, leading to a preview failure with this error. Following the advice in the documentation helped resolve it.
Thanks, @koalli! I'll try this out and see if I can reproduce the exact error. I'm a bit tied up until tomorrow but will aim to get to this by Friday. Thanks, everyone! |
Npm is installing and setting up prisma just fine. In fact you can prove this by deleting the .nuxt folder and doing a build. It will work perfectly. The first time. Build again and it fails. And the article you linked to with a fix doesn't work and is unrelated to this. There's a problem with how rollup is processing prisma and specifically the typescript portion. Something in prisma nuxt is not cooperating with rollup. I've been trying to debug the build step in Nuxt but haven't pinpointed it yet. |
Thanks for the insight, @gsxdsm!
I haven't been able to reproduce the exact error yet, as I haven’t tried @koalli's suggestion. In my case, I encountered the preview error linked here, which is why I mentioned it.
If you have any further insights or updates, I’d greatly appreciate it 🫶 ! |
You can create a new Nuxt project and add the nuxt-prisma module, then add one of these auth modules. I can still reproduce the RollupError the day before yesterday. |
Hey there @koalli, thanks so much for your suggestion and for your patience! Could you please check if this issue is resolved in version 0.1.3? It appears to be working fine on my end. 😊 |
@ankur-arch I tested version 0.1.3 and added the |
Getting this error after upgrading to 0.1.0
The text was updated successfully, but these errors were encountered: