prisma-upgrade-v7

Migrates Prisma ORM projects from v6 to v7 across all breaking changes.

2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/UdayPandey01/Healix --skill prisma-upgrade-v7-udaypandey01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-upgrade-v7
Source: https://github.com/UdayPandey01/Healix/tree/main/core/.agents/skills/prisma-upgrade-v7
Command: npx skills add https://github.com/UdayPandey01/Healix --skill prisma-upgrade-v7-udaypandey01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Upgrading from Prisma ORM v6 to v7 introduces breaking changes across the generator, driver adapters, configuration, and module system, and missing any one of them leaves a project with import errors, connection failures, or a non-functional client. ## Core Features & Use Cases - Complete migration path: Covers the new prisma-client generator, required output paths, driver adapter setup for SQL providers, prisma.config.ts creation, and explicit dotenv loading. - Detailed reference guides: Seven focused references on schema changes, driver adapters, ESM/CommonJS support, config, environment variables, removed features, and Accelerate users. - Removed feature replacements: Shows how to replace $use() middleware with Client Extensions, Prisma.validator with TypeScript satisfies, and removed CLI flags with explicit commands. - Use Case: A team upgrades to Prisma 7 and hits "Cannot find module" errors after regenerating the client; the skill walks them through fixing the generator output path, installing @prisma/adapter-pg, and updating client instantiation. ## Quick Start Ask the assistant to upgrade your project from Prisma 6 to Prisma 7 and it will apply the schema, config, adapter, and import changes step by step.

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 from Prisma 6 to Prisma 7?

Update @prisma/client and prisma to version 7, switch the generator provider to prisma-client with an explicit output path, create prisma.config.ts, install a driver adapter such as @prisma/adapter-pg, update client imports and instantiation, then run prisma generate.

What is the prisma-client generator in Prisma 7?

prisma-client is the default generator in Prisma 7, replacing prisma-client-js for current projects. It requires an explicit output directory instead of generating into node_modules and produces client, browser, models, and enums entrypoints.

Does Prisma 7 support MongoDB?

No. Prisma 7 has no MongoDB connector and no MongoDB driver adapter package. MongoDB projects should stay on the latest Prisma 6.x release or migrate to Prisma Next instead of following the standard v7 migration path.

Why does Prisma 7 require a driver adapter?

Prisma 7 removed the native engine binary from the SQL client path, so connections go through driver adapters like @prisma/adapter-pg or @prisma/adapter-mariadb that use native Node.js database drivers. This reduces bundle size and improves serverless compatibility.

How do I fix "Cannot find module" errors after upgrading Prisma?

Check that the generator output path in schema.prisma matches your import path, and confirm prisma generate ran successfully. Imports must point to the generated directory, for example ../generated/prisma/client, not @prisma/client.

What replaces Prisma.validator and $use middleware in v7?

Prisma.validator is replaced by TypeScript's satisfies operator applied to generated types like Prisma.UserSelect. The $use middleware API is replaced by Client Extensions using $extends with query hooks per model and operation.