prisma-orm-v7-skills

To upgrade Prisma ORM to v7, update @prisma/client and prisma packages to version 7, migrate your project to ES modules by setting type: "module" in package.json, move configuration to prisma.config.ts, and run prisma generate.

Prisma ORM v7 breaking changes include migrating to ES modules, moving datasource and config to prisma.config.ts, updating generator client output paths, and explicitly loading environment variables like dotenv/config.

To configure prisma.config.ts for environment variables, create the file at your project root, explicitly import dotenv/config at the top, and define your datasource configuration to properly load environment variables across platforms.

Yes, you need ES modules for Prisma v7 migration. You must set type: "module" in your package.json file and update Prisma Client imports to the generated output path, such as ./generated/prisma/client.

To generate the Prisma client after upgrading, run pnpm prisma generate. If you are using database migrations, run pnpm prisma migrate dev followed by pnpm prisma db seed to apply schema changes and seed data.

Yes, you can use Prisma v7 across multiple services and CI pipelines by applying the upgrade checklist uniformly. Update dependencies, configure prisma.config.ts, adapt ES module imports, and run prisma generate in each environment.