Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
prisma avatar

Prisma Upgrade V7 Schema Changes

  • 13 installs
  • 8 repo stars
  • Updated February 9, 2026
  • prisma/cursor-plugin

prisma-upgrade-v7-schema-changes updates schema.prisma for Prisma v7.

About

The prisma-upgrade-v7-schema-changes skill details generator migration from prisma-client-js with engineType to prisma-client with mandatory output directory outside node_modules. Remove engineType binary or library settings. Shows standard, monorepo, and same-directory output examples creating generated/client imports. Datasource block adjustments and preview feature renames accompany import path updates after prisma generate. Explains that v7 no longer drops client into node_modules by default so TypeScript imports must follow configured output. Switch generator provider to prisma-client. output path is mandatory for prisma-client generator. Remove engineType from generator block. Update imports to match configured output directory. Examples for monorepo and colocated output paths. schema.prisma generator block with output and new provider. User changes generator provider or output path for v7. Teams upgrading schema files during Prisma v7 migration. Build-phase integrations work updating Prisma schema for v7 generator.

  • Switch generator provider to prisma-client.
  • output path is mandatory for prisma-client generator.
  • Remove engineType from generator block.
  • Update imports to match configured output directory.
  • Examples for monorepo and colocated output paths.

Prisma Upgrade V7 Schema Changes by the numbers

  • 13 all-time installs (skills.sh)
  • Ranked #627 of 911 Databases skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
At a glance

prisma-upgrade-v7-schema-changes capabilities & compatibility

Capabilities
before and after generator blocks · key changes numbered list
Use cases
database · refactoring
From the docs

What prisma-upgrade-v7-schema-changes says it does

provider = "prisma-client"
SKILL.md
npx skills add https://github.com/prisma/cursor-plugin --skill prisma-upgrade-v7-schema-changes

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs13
repo stars8
Last updatedFebruary 9, 2026
Repositoryprisma/cursor-plugin

How do I update Prisma generator for v7?

Update schema.prisma generator block for Prisma v7 prisma-client provider and required output paths.

Who is it for?

Teams upgrading schema files during Prisma v7 migration.

Skip if: Skip when generator already uses prisma-client output.

When should I use this skill?

User changes generator provider or output path for v7.

What you get

schema.prisma generator block with output and new provider.

Files

SKILL.mdMarkdownGitHub ↗

Schema Changes

Prisma v7 introduces a new prisma-client generator. Update your generator block and import paths accordingly.

Generator Provider

Before (v6)

generator client {
  provider = "prisma-client-js"
  engineType = "binary"  // or "library"
}

After (v7)

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

Key Changes

1. Provider name

Use prisma-client in Prisma v7.

2. Output is required (for prisma-client)

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"  // Required for prisma-client
}

3. Engine type removed

engineType is removed in Prisma v7. Remove any engineType setting from your generator block.

Example Output Paths (prisma-client)

Standard project

output = "../generated"

Creates: generated/client

Monorepo

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

Same directory as schema

output = "./generated"

Creates: prisma/generated/client

Datasource Block

The url, directUrl, and shadowDatabaseUrl values now live in prisma.config.ts in Prisma v7. Keep only the provider in schema.prisma:

Before (v6)

datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
}

After (v7)

datasource db {
  provider = "postgresql"
  // URLs configured in prisma.config.ts
}
// prisma.config.ts
export default defineConfig({
  datasource: {
    url: env('DATABASE_URL'),
    directUrl: env('DIRECT_URL'),
    shadowDatabaseUrl: env('SHADOW_DATABASE_URL'),
  },
})

Full Example

v6 Schema

generator client {
  provider   = "prisma-client-js"
  engineType = "library"
}

datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
}

v7 Schema

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

datasource db {
  provider = "postgresql"
}

After Schema Changes

1. Run prisma generate:

   npx prisma generate

2. Update imports throughout your codebase:

   // Before (prisma-client-js)
   import { PrismaClient } from '@prisma/client'
   
   // After (prisma-client, output = "../generated")
   import { PrismaClient } from '../generated/client'

3. Update .gitignore (if using prisma-client output):

   generated

Preview Features

Preview features work the same:

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

Related skills

FAQ

What does prisma-upgrade-v7-schema-changes do?

prisma-upgrade-v7-schema-changes updates schema.prisma for Prisma v7.

When should I use prisma-upgrade-v7-schema-changes?

User changes generator provider or output path for v7.

Is this skill safe to install?

Review the Security Audits panel on this page before installing in production.

Databasesdatabases

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.