ArmoHotspot/backend/.agents/skills/prisma-upgrade-v7/references/schema-changes.md

Schema Changes

Prisma v7 promotes prisma-client to the default generator. Update your generator block, output path, and imports accordingly.

This guide is for projects that are actually migrating to Prisma 7. Do not apply these schema changes to MongoDB projects; keep those on Prisma 6.x.

Generator Block (v7)

generator client {
  provider = "prisma-client"
  output   = "../generated/prisma"
}

Key Changes

1. Provider name

Use prisma-client in Prisma v7. The older prisma-client-js generator still exists in the repo for legacy setups, but prisma-client is the default path for current projects.

2. Output is required

The output field is mandatory when using prisma-client. Prisma Client no longer generates to node_modules with this generator.

generator client {
  provider = "prisma-client"
  output   = "../generated/prisma"
}

3. engineType changed

Legacy Rust engine settings are gone. With prisma-client, the relevant value is engineType = "client" if you want to state it explicitly, although it is typically inferred and can be omitted.

generator client {
  provider   = "prisma-client"
  output     = "../generated/prisma"
  engineType = "client"
}

4. moduleFormat is explicit when needed

If you must stay on CommonJS:

generator client {
  provider     = "prisma-client"
  output       = "../generated/prisma"
  moduleFormat = "cjs"
}

Example Output Paths

Standard project

output = "../generated/prisma"

Creates files like:

generated/prisma/
  client.ts
  browser.ts
  enums.ts
  models.ts
  models/

Monorepo

output = "../../packages/database/generated/prisma"

Same directory as schema

output = "./generated/prisma"

Creates: prisma/generated/prisma/client.ts

Datasource Block

The url, directUrl, and shadowDatabaseUrl fields in the datasource block are deprecated in Prisma v7. Move them to prisma.config.ts and keep only the provider in schema.prisma:

datasource db {
  provider = "postgresql"
}

export default defineConfig({
  datasource: {
    url: env('DATABASE_URL'),
    directUrl: env('DIRECT_URL'),
    shadowDatabaseUrl: env('SHADOW_DATABASE_URL'),
  },
})

After Schema Changes

1. Run prisma generate:

   npx prisma generate
   

2. Update imports throughout your codebase:

   import { PrismaClient } from '../generated/prisma/client'
   

3. Update .gitignore if you manage this manually:

   /generated/prisma
   

4. Replace Prisma.validator() with TypeScript satisfies when using prisma-client:

   import { Prisma } from '../generated/prisma/client'
   
   const userSelect = {
     id: true,
     email: true,
   } satisfies Prisma.UserSelect
   

Generated Entrypoints

• client - server-side Prisma Client and Prisma namespace
• browser - browser-safe types and enums without a real PrismaClient
• enums - slim enum-only entrypoint
• models - model types and derived helper types

Preview Features

Preview features still work as before:

generator client {
  provider        = "prisma-client"
  output          = "../generated/prisma"
  previewFeatures = ["relationJoins", "fullTextSearch"]
}

Recent preview-feature examples also include partialIndexes for PostgreSQL, SQLite, SQL Server, and CockroachDB:

generator client {
  provider        = "prisma-client"
  output          = "../generated/prisma"
  previewFeatures = ["partialIndexes"]
}