Skip to content

Prisma engine binary not bundled with workflow steps on Vercel #1956

Description

@anthopit

Hey, running into a Prisma + Vercel Workflow issue.

When a workflow step uses @prisma/client, the bundle at /var/task/index.js
ships without the engine binary next to it. Step crashes on first DB call.

Error:
PrismaClientInitializationError:
Invalid prisma.integration.findUnique() invocation:

Prisma Client could not locate the Query Engine for runtime "linux-arm64-openssl-3.0.x".

This is likely caused by a bundler that has not copied "libquery_engine-linux-arm64-openssl-3.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-linux-arm64-openssl-3.0.x.so.node" has been copied next to the bundle or in "node_modules/.prisma/client".

Same Prisma client works fine from regular API routes on the same deploy, only the workflow bundle is missing the .so.node.

Setup

  • workflow@4.2.4, nuxt@3.13, prisma@5.19, @prisma/client@5.19
  • Node 22 on Vercel
  • binaryTargets = ["native", "rhel-openssl-3.0.x",
    "linux-arm64-openssl-3.0.x"]

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions