prisma-orm-v7-skills

Migrating Prisma ORM to v7 requires updating the generator provider to prisma-client with an explicit output path, moving datasource config to prisma.config.ts, enforcing ES module compliance, and running prisma generate and db seed.

Breaking changes in Prisma v7 include switching the generator provider to prisma-client, requiring an explicit output path for generated clients, migrating datasource configuration to prisma.config.ts, and enforcing ES module compliance with explicit environment handling.

Yes, ES module compliance is an enforced requirement for Prisma v7. You must update your Node.js and TypeScript project configuration to support ES modules alongside updating prisma.config.ts for explicit environment handling.

You configure prisma.config.ts in Prisma v7 by migrating datasource configuration into it and establishing explicit environment handling, replacing previous schema-based datasource blocks to ensure proper ES module variable loading.

Yes, Prisma v7 works in TypeScript monorepos. Teams can follow the v7 upgrade checklist to adjust prisma schema files, update import paths, and configure environment variables across workspace packages after migrating.

Prisma imports break after upgrading to v7 because the generator provider changed to prisma-client with a required explicit output path. You must update import paths to match the new generated client location after running prisma generate.