Production nuxt build is faulty when using nuxt-prisma with pnpm, frontend logic crashes out

[wjdp]

I'm using pnpm which may compound this problem

I have installed this package and done the following extra items as described in the Prisma docs

• Added hoist-pattern[]=*prisma* to .npmrc
• Added a vite resolve alias as per the linked doc

I now have working API routes and a working frontend when running in dev mode, however when running in production mode I'm getting the following which causes my frontend logic to brick:

Clicking through Qg seems to be related to the prisma client.

I'm not importing the prisma client on the frontend pages at all. Why is it being loaded and why is it crashing out those pages?

Here is the current state of my repo https://github.com/wjdp/grate/tree/b7dd02dd354e48cb4286e9f606ca9cef59869440

When I say the frontend is bricked, this very simple page stops working: https://github.com/wjdp/grate/blob/b7dd02dd354e48cb4286e9f606ca9cef59869440/pages/state.vue

Browing through this repos issues there seems to be a handful of similar problems but none that exactly match this one, hence opening a new issue.

[wjdp]

I've spun up a branch that throws out pnpm and replaces with npm and this seems to fix the problems. Seems like a pnpm problem. Any ideas how to get this to work, is this a me problem or a bug with the project?

[ankur-arch]

Hey @wjdp , thanks for taking the time and opening the issue.

I would suspect it's a possible issue with the project, given we've had issues with pnpm in the past. Could you provide some exact steps for me to reproduce the issue?

I'm not being able to reproduce it using pnpm v9.6.0, hence a reproduction with a version number would be helpful for me to debug the issue.

[wjdp]

Hey @ankur-arch thank you for the interest. Have you attempted to repro with the linked repo? I'm running pnpm 9.12.0 locally when testing. The docker build exhibits the same problem and is just calling npm install -g pnpm without a lock to a version.

I've also run through the steps that trigger this behavior in a new repo. This problem seems to stem from prisma/prisma#13946 and the vite.resolve fix I've attempted to add for it.

See the example repo: https://github.com/wjdp/prisma-pnpm
I've tried to make the commits "one step at a time" so you can walk through what I'm doing.

[wjdp]

OK I think I have a solution for this: wjdp/grate@9ac0ddb

prisma generate was placing the client inside node_modules/prisma/client (actually somewhere else but is a symlink)
The advice online was talking about node_modules/.prisma/client, tried forcing prisma to output there and I think I have it working now.

If this is how this should be set up may be worth adding to the documentation.

[AmanVarshney01]

Sadly, we are deprecating this module. You can read more about the explanation here

How to use Nuxt with Prisma 7 - https://www.prisma.io/docs/guides/nuxt