-
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
Resolve issues when installing the Prisma client in a PNPM workspace using Nuxt layers #30
base: main
Are you sure you want to change the base?
Resolve issues when installing the Prisma client in a PNPM workspace using Nuxt layers #30
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Please note: on this version of the PR, installation will happen in the wrong Nuxt layer. A workaround for now is to manually install the client and set the |
I'm back! @ankur-arch I would like to add two configuration options, but I'd like your thoughts on it:
I think especially the second option would benefit a lot of people, since I don't see a way that we can detect it in the code in a reliable and performant manner. |
Thanks @Dobefu! I'll check on this the next week as I'm on limited availability this week. |
@ankur-arch will be really nice if this could be checked. Many users of nuxt-prisma are using layers and if already there is a solution to this issue, why not to use it. |
Just to check if the issue I had was related to this and not something else, I switched to npm and it worked. So it was definetely caused by lack of pnpm support. Switching to npm can be a workaround for now |
Hey @Dobefu 👋, This has been in draft for a while, so I wanted to check in to see if you’re planning to get to this. Thanks for your contributions so far—they’ve been really valuable 🔥 ! Let me know if you’re planning to pick this up; otherwise, I’ll move forward with the updates to ensure compatibility with other package managers and Nuxt layers, as I’d like to proceed soon. Looking forward to hearing from you and possibly collaborating again 😄 ! |
Hi @ankur-arch! I'm certainly open to collaborate again! To be quite honest, I was waiting for your thoughts on #30 (comment) and then proceeded to... kind of forget to follow up on it 😅. My apologies. What are your thoughts on the configuration options in my previous comment? If they're alright to add, I can look into it this weekend. |
…ckage-manager-cannot-get-resolved
Alrighty, I've fixed the merge conflicts. |
Hi @ankur-arch, Have you had time to look into this, yet? |
Hey @Dobefu 👋 , I apologize for my recent absence; I've been busy with other commitments. It's great to have you back, and I really appreciate you taking the time to work on this PR and resolve the merge conflicts.
Since this PR is from a fork, GitHub won't allow the preview package to be published through the workflow, so I'll need to test it manually.
The options look good to me! I'll test the PR tomorrow and then proceed with merging it. I'll also review any accompanying documentation changes to ensure everything is consistent. |
Hey @Dobefu 👋, I gave the PR a try and still have a few tests left to go. Sorry for the delay—I'll wrap it up on Monday! 😊 |
This PR will fix #29