prisma-upgrade-v7

Migrate Prisma ORM v6 projects to v7 with generator and client updates.

1|Updated May 1, 2026
One-click install
npx skills add https://github.com/Joshkovu/ghost-ai --skill prisma-upgrade-v7-joshkovu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-upgrade-v7
Source: https://github.com/Joshkovu/ghost-ai/tree/main/.agents/skills/prisma-upgrade-v7
Command: npx skills add https://github.com/Joshkovu/ghost-ai --skill prisma-upgrade-v7-joshkovu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents broken builds and runtime failures when migrating a project from Prisma ORM v6 to v7 by providing a complete, breaking-changes-focused upgrade path.

Core Features & Use Cases

  • End-to-end v6 → v7 Migration Guide: Covers generator changes, required output paths, new client entrypoints, and updated import/instantiation patterns.
  • Driver Adapter Integration for SQL: Explains how to install and configure the correct @prisma/adapter-* packages and how adapter requirements differ by provider and pooling behavior.
  • ESM-first and Environment Loading Fixes: Addresses ESM/CommonJS compatibility via moduleFormat = "cjs" and resolves the need for explicit .env loading using prisma.config.ts + dotenv.
  • Use Case: When your application fails after upgrading Prisma (for example import errors, missing generated files, or connection/adapter misconfiguration), this Skill helps you identify the exact change causing it and apply the correct fix across schema, config, and runtime client code.

Quick Start

Ask the AI to produce a Prisma v7 upgrade plan for your stack (Node.js version, ESM vs CommonJS, database provider, and whether you use Accelerate) starting from your current generator block and prisma.config.ts status.

Frequently Asked Questions about prisma-upgrade-v7

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade Prisma ORM from v6 to v7 without breaking my build?

Upgrading Prisma ORM to v7 requires updating the prisma-client generator, modifying the schema generator output path, and adjusting client import and instantiation patterns to prevent broken builds and runtime failures.

Why does my Prisma 7 migration fail with module import or missing generated entrypoint errors?

Prisma 7 migration failures with module import or missing generated entrypoint errors occur because the new client entrypoints require updated import paths and explicit ESM or CommonJS moduleFormat configuration.

Do I need a SQL driver adapter when upgrading to Prisma v7?

Yes, Prisma v7 enforces SQL driver adapter usage for supported databases, requiring you to install and configure the correct @prisma/adapter-* packages based on your specific provider and pooling behavior.

How do I load environment variables in Prisma 7 using prisma.config.ts?

Loading environment variables in Prisma 7 requires implementing a prisma.config.ts file combined with dotenv to explicitly load environment variables, replacing previous automatic environment loading behaviors.

Can I use Prisma 7 with a CommonJS module format instead of ESM?

Yes, Prisma 7 supports CommonJS compatibility by setting moduleFormat to cjs in your configuration, providing an alternative to the default ESM-first approach for projects not yet using ES modules.

What are the Node.js and TypeScript version requirements for Prisma v7?

Prisma v7 requires Node.js version 20.19.0 or higher and TypeScript version 5.4.0 or higher to ensure compatibility with the updated generator and client instantiation workflow.