Resolve issues when installing the Prisma client in a PNPM workspace using Nuxt layers

[Dobefu]

This PR will fix #29

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nuxt-prisma	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 13, 2024 2:19pm

[Dobefu]

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 installPrismaClient option to false.
I do not have much time to look into this further for a couple of days, so I hope this is a helpful start at least.

[Dobefu]

I'm back!

@ankur-arch I would like to add two configuration options, but I'd like your thoughts on it:

• packageManager
  • Will allow users to skip the whole filesystem checks, and is less error-prone
  • This will be optional, and fall back to the current detection method
• prismaRoot
  • Will allow users to customise where Prisma does its thing
  • Will resolve Usage with a layer based architecture #16
  • Will resolve Package manager cannot get resolved when using Nuxt Layers #29
  • Will probably resolve Failed on initial start (bun) #31

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.

[ankur-arch]

Thanks @Dobefu! I'll check on this the next week as I'm on limited availability this week.

[husayt]

@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.

[husayt]

@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