Skip to content

Build Fails on Vercel Due to Missing @prisma/client-runtime-utils Module #6

@Saisathvik94

Description

@Saisathvik94

Build Fails on Vercel Due to Missing @prisma/client-runtime-utils Module

Description

The Vercel deployment fails during the Next.js build step because the generated Prisma client attempts to import @prisma/client-runtime-utils, which cannot be resolved by Turbopack.

What Happened?

The build completes dependency installation and Prisma client generation successfully, but fails during next build with multiple instances of:

Module not found: Can't resolve '@prisma/client-runtime-utils'

The errors originate from:

packages/db/generated/runtime/client.js

and affect both App Routes and Server Components that import the shared database package.

Expected Behavior

The application should build successfully after Prisma client generation without unresolved runtime dependencies.

Actual Behavior

Turbopack reports multiple module resolution errors for:

@prisma/client-runtime-utils

causing the build to fail.

Error Snippet

Module not found: Can't resolve '@prisma/client-runtime-utils'

Import trace:
./packages/db/generated/runtime/client.js
./packages/db/generated/index.js
./packages/db/generated/client.js
./packages/db/dist/index.js

Additional Notes

  • Prisma client generation succeeds without errors.
  • The generated runtime code references @prisma/client-runtime-utils, but the package is not available during the Next.js build.
  • The issue appears after upgrading to Prisma 7.x and may be related to generated client runtime dependencies in monorepo/Turbopack environments.
  • Prisma schema also reports:
Preview feature "driverAdapters" is deprecated.

Reproduction Steps

  1. Clone the repository.
  2. Run:
pnpm install
pnpm --filter @queuely/db generate
pnpm turbo run build --filter=@queuely/web
  1. Observe build failure with unresolved @prisma/client-runtime-utils imports.

Possible Cause

The generated Prisma client includes a runtime dependency on @prisma/client-runtime-utils, but the package is not installed, hoisted, or bundled correctly within the monorepo build environment.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions