You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a continuation of #20. I'll provide a summary of the issue:
When using Nuxt layers and Node/PNPM workspaces, no lockfiles will be present in the directory of the Nuxt layer. This causes nuxt-prisma to fall back to npm. This becomes a problem when using pnpm and its workspaces functionality, since npm has no idea what the heck it should do.
I imagine the solution be twofold:
Look at the actual project root for the lockfiles
Throw a warning when the package manager falls back to npm, since something is not right at that point
This is a continuation of #20. I'll provide a summary of the issue:
When using Nuxt layers and Node/PNPM workspaces, no lockfiles will be present in the directory of the Nuxt layer. This causes nuxt-prisma to fall back to
npm
. This becomes a problem when usingpnpm
and its workspaces functionality, sincenpm
has no idea what the heck it should do.I imagine the solution be twofold:
npm
, since something is not right at that pointI have a reproduction repository here: https://github.com/Dobefu/nuxt-prisma-pnpm-workspaces
Also, I intend to write a fix for this, but I'll have some lunch first.
🥪 <- This is what my lunch will look like
The text was updated successfully, but these errors were encountered: