Home Search Pricing Get inErrata About

Sign in Sign up

Graph/prisma-runtime-artifact-mismatch

Pattern

Bundled Runtime Mismatch

prisma-runtime-artifact-mismatch

A recurring build-versus-deploy failure where Prisma artifacts are generated or routed for a different runtime (OpenSSL target, query engine location, or pooler port), leading to missing exports/engines or incorrect connection behavior only after deployment.

Node Details

Public graph metadata

Updated5/1/2026

Connections

30 linked nodes

Unhandled Runtime Error Error: Cannot find module '@tanstack/query-core' — when i try "yarn run dev".

EPERM: operation not permitted, symlink. Outcome: Build error occurred.

Type instantiation is excessively deep and possibly infinite — in a monorepo/workspace project. Tension: on seemingly benign types like this. Outcome: I've found this is almost always due to a mismatched dependency between 2 packages in your repository.

When publishing the Vite-built package, the generated dist output includes internal build artifacts such as node_modules/_virtual and/or breaks dependency resolution because subpath imports like react/jsx-runtime aren’t treated as externals. This results in unwanted contents being packaged and incorrect bundling for NPM publication.

Webpack has trouble bundling the shared library when imports resolve as "../shared/..."

the build is now failing with these raw logs — I've swapped my package manager to pnpm for a SvelteKit app. Tension: This is caused by Rollup reading the `canvas.node` binary, which shouldn't even be in the build output. Outcome: the build is now failing with these raw logs.

it doesn't include the `@my-app/shared` into the bundle — when I run the development server. Tension: Instead it just shows the placeholder. Outcome: the angular compiler does not bundle the module.

Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x". — when I deploy. Tension: This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle. Outcome: Ensure that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied next to the bundle or in "generated/prisma".

Error: Failed to collect page data for /api/favourites/[drivingSchoolId]. Tension: the build process exits with code 1. Outcome: override Build command to `npx prisma generate && next build`.

missing_connection_string': You did not supply a 'connectionString' and no 'POSTGRES_URL' env var was found. — when I was deploying my next application or excute "pnpm run build". Tension: Build error occurred Error: Failed to collect page data for /seed.

Deploying to Vercel fails to apply the desired npm install flags (e.g., `--legacy-peer-deps`), causing dependency/peer conflicts during deployment.

Type error: Module '"@prisma/client"' has no exported member 'Product'. — when i am trying to deploy a project on Vercel. Tension: Everything works fine when i run "npm run build". But when i am trying to deploy a project on Vercel.

The SvelteKit 2 (with Svelte 4) app runs correctly locally but fails during deployment on Vercel with a deployment/runtime error shown in the Vercel logs.

the stack trace is obfuscated and I see the source maps are not uploaded — when I create a release build locally or through EAS build. Tension: The release this event belongs to doesn't have any uploaded artifacts. Outcome: Ensure that your project is using the Sentry Metro Plugin in `metro.config.js`.

Bitrise Android release builds fail at `:package_info_plus:compileReleaseJavaWithJavac` with `error: invalid source release: 17`. The same project builds locally in release/development.

Zone mismatch. — during runApp. Tension: The Flutter bindings were initialized in a different zone than is now being used. Outcome: This will likely cause confusion and bugs as any zone-specific configurat.

"The projectSettings object is required for new projects, but is missing in the deployment payload" — When I'm trying to promote deployment to production. Tension: No any documentation about such error is marked anywhere. Outcome: Any workarounds?

"Unable to download artifact(s): Artifact not found for name: build" — Deploy Workflow: Deploys to Firebase Hosting, triggered via workflow_run after a successful build. Tension: The Build workflow successfully uploads the build artifact, but the Deploy workflow fails.

Deployment fails silently when code includes azure-identity

When this import is removed, deployment works fine. Outcome: deployment works fine.

I get an error related to my third party frameworks (Firebase and others) added via SPM. — the app builds and archives fine locally but from GitHub action is produces errors. Tension: I've tried various combinations of arguments for xcode build but without success.

Execution failed for task ':app:mergeReleaseJavaResource'. — In the Run Gradlew step in expo. Tension: 2 files found with path 'org/bouncycastle/pqc/crypto/picnic/lowmcL5.bin.properties' from inputs. Outcome: Adding a packaging block may help.

The error occurs during the build/deployment process in AWS Amplify — a Next.js (v13+) API route that handles Stripe webhooks. Tension: I can't pinpoint the exact cause. Outcome: Solved by using this version of SDK.

Inconsistent JVM-target compatibility detected for tasks 'compileDebugJavaWithJavac' (1.8) and 'compileDebugKotlin' (17). Tension: Execution failed for task ':stripe_android:compileDebugKotlin'. Outcome: BUILD FAILED in 14s.

CDK keeps referencing the old bootstrap qualifier (hnb659fds) and fails with the following error — during deployment. Outcome: SSM parameter /cdk-bootstrap/hnb659fds/version not found.

Error: host settings conflict with another service. Tension: They are both in the kamal docker network (bridge), and are exposed through kamal-proxy container. Outcome: I can deploy both backend and frontend independently.

We run `dotnet list .sln package --vulnerable --include-transitive --source https://api.nuget.org/v3/index.json` nightly on our CI server. Tension: update the runtime on our CI server and instruct our customer to do the same on their machines.

Running an old React app on Node.js >18 fails during `npm start` with an error related to webpack/OpenSSL compatibility, and the environment variable `SKIP_FLIGHT_CHECK` plus OpenSSL legacy provider workaround is being considered.

Adding nondeterministic compilation breaks reproducible builds — users will no longer be able to verify the packages they install. Tension: this security measure is a good example of so-called security theater. Outcome: it will not provide additional security for most of the cases, but will greatly complicate a lot of things.

The code generator in pipeline builds the package into the deployment JAR. — building a code generation tool using JHipster. Tension: Beside approved code scanning tools, what else can be done here on security front ?

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata