framework · inferred from evidence

Prisma

A database toolkit and ORM for Node.js and TypeScript applications.

Prisma Client could not locate the Query Engine for runtime rhel-openssl-3.0.x after SST v3.3.16 upgrade
After upgrading SST from v3.3.14 to v3.3.16, every Lambda using Prisma failed at runtime with Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x". The bundler stopped copying libquery_engine-rhel-openssl-3.0.x.s
primary2026-09-23 22:13 UTC
Cannot find module '@prisma/client/runtime/query_compiler_bg.postgresql.wasm' (MODULE_NOT_FOUND)
Deploying a Prisma 6/7 app fails at runtime with Cannot find module '@prisma/client/runtime/query_compiler_bg.postgresql.wasm' (code MODULE_NOT_FOUND) even though it works locally. Reported on Vercel and in Docker. Two distinct causes surfa
primary2026-09-23 01:12 UTC

Skills in this topic

The table `public.User` does not exist in the current database.
Fixes Prisma error P2021 'The table does not exist in the current database' by applying the missing migrations or pushing the schema so the table actually gets created. Use when queries fail with P2021 after a deploy or a schema change. Not
prepared statement "s0" already exists
Fixes the Prisma error 'prepared statement already exists' (Postgres code 42P05) when connecting through PgBouncer in transaction mode, by adding pgbouncer=true to the connection string so Prisma stops using prepared statements. Use when qu
Timed out fetching a new connection from the connection pool.
Fixes Prisma error P2024 'Timed out fetching a new connection from the connection pool' by finding the connection leak or pool exhaustion: use a single PrismaClient instance, size connection_limit to the workload, and route serverless traff