prisma-orm-v7-skills_skill

Overview

This skill summarizes key facts and breaking changes when upgrading to Prisma ORM 7. It highlights required runtime/tooling versions, ESM migration implications, schema and generator updates, driver adapter requirements, and CLI/config behavior changes. Use it to check compatibility and plan migration steps before generating code or troubleshooting upgrade issues.

How this skill works

The skill inspects the major compatibility and behavior changes introduced in Prisma 7 and translates them into actionable items: required Node/TypeScript versions, generator and schema changes, where to configure datasources, and how to instantiate the client. It also flags removed features (middleware, metrics, certain env vars), changed defaults (no automatic .env loading, no auto-generate), and database support limitations (no MongoDB). Finally, it produces a concise upgrade checklist to apply in a project.

When to use it

• Before upgrading project dependencies from Prisma 6 to Prisma 7
• When migrating a codebase from CommonJS to ESM to support Prisma 7
• When troubleshooting Prisma Client import or generation failures after upgrading
• When preparing CI/workflow steps that run prisma generate, migrate, or seed
• When evaluating whether to stay on Prisma 6 due to MongoDB requirements

Best practices

• Confirm Node.js >= 20.19.0 and TypeScript >= 5.4.0 before upgrading
• Migrate the project to ESM or set "type": "module" and adjust TS config (module: ESNext, target: ES2023, moduleResolution: node)
• Add prisma.config.ts at repo root and explicitly load environment variables (e.g., import 'dotenv/config')
• Change generator provider to prisma-client, set output, run pnpm prisma generate, and update imports to the generated path
• Replace prisma.$use middleware with Prisma Client Extensions and use driver adapters for DB connections
• Run prisma generate and prisma db seed explicitly in scripts or CI — do not rely on automatic behavior

Example use cases

• Upgrading a Next.js app to use Prisma 7 and adjusting imports to a generated client directory
• Adding a driver adapter (e.g., @prisma/adapter-pg) when instantiating Prisma Client for Postgres
• Moving datasource connection settings from schema.prisma to prisma.config.ts and loading .env explicitly
• Updating CI workflows to call pnpm prisma generate and pnpm prisma db seed as explicit steps
• Deciding to stay on Prisma 6 if the project depends on MongoDB support