Prisma cannot find wasm module all of a sudden? no changes to versions or schema
I have a simple postgres setup, merely trying to generate models whether within a pipeline when creating a docker container or on my local machine, as of this morning i'm getting this error:
and i can't build my project, we have a critical bug fix due asap and this is a major blocker as we can no longer build our images, no obvious fix either
8 Replies
You decided to hold for human wisdom. We'll chime in soon! Meanwhile,
#ask-ai is there if you need a quick second opinion.seems to be pnpm related
switched to npm but that can have unforseen consequences in other parts of the app, i'll try to find a way to make it work
Just to confirm, switching to npm fixed the issue for you?
i am also getting a similar error since the update
Are you also using pnpm?
using yarn
@Nurul (Prisma) yeah using npm over pnpm has fixed the issue, which i hope is temporary as i'd much preffer to go back to pnpm -- but again this has happened fully out of the blue, i haven't updated neither pnpm, npm, node, prisma, nothing!
just woke up one morning and it stopped working entirely, i deploy 2-3 times a day easily across the various services we have
Hmm, strange! I haven't encountered this kind of issue before.
It would be interesting to see if the issue gets fixed with the release of version 6.17.0