prisma-knowledge-patch

Guide Prisma v6 to v7 migrations with code changes for TypeScript projects.

22|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill prisma-knowledge-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-knowledge-patch
Source: https://github.com/Nevaberry/nevaberry-plugins/tree/main/plugins/prisma-knowledge-patch/skills/prisma-knowledge-patch
Command: npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill prisma-knowledge-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill captures and explains the breaking changes and new workflows introduced in Prisma after the model training cutoff, focusing on the v7 ESM rewrite and related migration tasks so engineers avoid outdated patterns, broken imports, and misconfigured tooling.

Core Features & Use Cases

  • Clear mapping of breaking changes: new generator name and required output, ESM-only module expectations, and moved CLI configuration into prisma.config.ts.
  • Practical migration steps: update imports to the generated client path, install and configure driver adapters, replace middleware with client extensions, and run explicit generate and seed commands.
  • Developer observability and SQL features: guidance on SQL comments, TypedSQL usage, compilerBuild options, and connection/SSL considerations for production deployments.
  • Use Case: Upgrade a TypeScript Node.js project from Prisma v6 to v7 to ensure the generated client, adapters, and migration workflows work correctly and follow best practices.

Quick Start

Upgrade my TypeScript project from Prisma v6 to v7 and produce a step-by-step migration plan showing exact package installs, prisma.config.ts changes, generator/output updates, adapter installation, and import refactors.

Frequently Asked Questions about prisma-knowledge-patch

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

FAQPage Schema
How do I migrate Prisma to ESM-only modules and update the generator output path?

To migrate Prisma to ESM, set explicit client generation with an output path in your generator configuration, update imports to match the generated client path, and ensure your Node.js TypeScript project uses ESM module configuration throughout.

What is the correct way to configure driver adapters in a Prisma v7 TypeScript project?

Configuring driver adapters in Prisma requires installing the specific required adapter packages, updating your database connection logic to use the adapter, and verifying connection and SSL considerations for production deployments.

How do I move CLI configuration to prisma.config.ts when upgrading Prisma?

Moving CLI configuration to prisma.config.ts involves creating the configuration file in your project root, transferring your schema generator settings and compilerBuild options into it, and running explicit generate commands to verify the setup.

Can I still use middleware in Prisma or do I need to convert to client extensions?

Prisma middleware is replaced by client extensions in newer versions. You must convert your existing middleware logic to client extensions to maintain custom query behavior and ensure compatibility with driver adapters.

What TypeScript and Node.js minimum versions are required for a Prisma v7 upgrade?

Upgrading Prisma v7 requires meeting specific Node.js and TypeScript minimum version requirements to support ESM-only modules and driver adapters, ensuring your TypeScript Node.js codebase can compile and run correctly.

How do I use TypedSQL and SQL comments in a Prisma migration?

TypedSQL usage and SQL comments are configured through compilerBuild options and prisma.config.ts settings, allowing you to execute typed SQL queries while maintaining developer observability for database operations.