Prisma
Backend & InfraNext-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
Release History
7.4.28 fixesThis 7.4.2 patch release focuses primarily on resolving various bug fixes across Prisma Client, Driver Adapters (specifically MariaDB), and the Schema Engine.
7.4.17 fixes2 featuresThis 7.4.1 patch release focuses primarily on bug fixes across Prisma Client, Driver Adapters, and the Prisma Schema Language, alongside minor quality improvements.
7.4.06 fixes4 featuresVersion 7.4.0 introduces a significant query compilation caching layer to improve performance under concurrency and adds support for Partial Indexes across several databases. Numerous community contributions fixed various bugs related to migrations, BigInt handling, and database connection stability.
7.3.0Breaking3 fixes2 featuresPrisma 7.3.0 introduces performance tuning via the `compilerBuild` option for the ORM client and allows raw queries to bypass the query compiler. This release also reverts a breaking change related to mapped enums and fixes BigInt precision issues in PostgreSQL JSON aggregations.
6.19.21 fixThis 6.19.2 patch release fixes an issue related to Prisma Accelerate support in specific edge runtime configurations.
7.2.0Breaking6 fixes4 featuresPrisma 7.2.0 introduces a new SQL commenter plugin, flexible URL configuration for migration commands, and runtime-aware initialization for Bun, alongside critical fixes for byte upserts and error reporting.
6.19.11 fixThis patch release fixes a regression in Prisma 6.13.1 where schema diffing incorrectly reported empty results.
7.1.02 fixes6 featuresPrisma 7.1.0 introduces SQL Commenter support for enhanced query observability and tracing, alongside TypeScript improvements for pnpm monorepos and the env() helper.
7.0.16 fixes4 featuresPrisma 7.0.1 is a patch release focusing on quality of life improvements, restoring CockroachDB support, and fixing regressions in Prisma Studio and the CLI.
7.0.0Breaking3 featuresPrisma 7.0.0 makes the ESM-based Prisma Client the default, significantly reducing bundle sizes and improving performance. It introduces a mandatory configuration file (prisma.config.ts) and requires explicit driver adapter injection and output paths.
6.19.02 fixes4 featuresPrisma 6.19.0 introduces connection pooling for Prisma Postgres, local database support in the VS Code extension, and various ORM improvements to prepare for the v7 major release.
6.18.07 featuresPrisma 6.18.0 introduces the prisma.config.ts configuration file as the new standard for settings like datasources and engines, preparing users for the upcoming Prisma v7.
6.17.11 fixThis patch release fixes a regression introduced in v6.17.0 that caused incorrect diffing and migrations for fields marked as Unsupported.
6.17.02 fixes4 featuresPrisma 6.17.0 introduces Entra ID support for MS SQL Server, stabilizes direct connections for Prisma Postgres, and provides new usage metrics in the Prisma Console.
6.16.35 fixesA patch release focusing on fixing JSON null types in browser builds, restoring migration behavior for multi-tenancy, and resolving a memory leak in the MariaDB adapter.
6.16.22 fixesThis patch release fixes validation rules for Prisma Postgres and resolves runtime errors in non-NodeJS environments caused by timer unreferencing.
6.16.11 fixThis patch release fixes a bug where stabilized features still required preview flags in edge runtimes like Vercel Edge and Cloudflare Workers.
6.16.0Breaking6 featuresPrisma 6.16.0 marks the General Availability of the Rust-free ORM architecture and the new ESM-first 'prisma-client' generator, significantly reducing bundle sizes and improving type-checking performance.
6.15.0Breaking1 fix7 featuresPrisma 6.15.0 introduces AI safety guardrails for destructive CLI commands, simplifies Client runtime configurations, and moves the Prisma Postgres Management API to General Availability.
6.14.0Breaking3 fixes4 featuresPrisma 6.14.0 re-introduces @unique attributes for SQL views in Preview and removes the long-deprecated prisma.$use middleware method. The release also focuses on type performance improvements and stability fixes for the upcoming Prisma 7 engine changes.
6.13.0Breaking1 fix6 featuresPrisma 6.13.0 promotes Prisma Config and Multi-schema support to General Availability and introduces externally managed tables. It also refines SQL views support by removing incompatible attributes and adds pgvector support to Prisma Postgres.
6.12.04 featuresPrisma 6.12.0 introduces the ESM-compatible prisma-client generator in Preview and adds configuration options for migrations and views paths in prisma.config.ts.
6.11.12 fixesThis patch release fixes a Prisma Client initialization error involving Prisma Accelerate and connection strings, as well as a data mapping error in array aggregations.
6.11.03 fixes7 featuresPrisma 6.11.0 introduces Preview support for Rust-free engines for MySQL, Neon, and CockroachDB, adds new CLI commands for managing local Postgres instances, and enables embedding Prisma Studio via a new core package.
6.10.12 fixesPrisma 6.10.1 is a patch release fixing PostgreSQL connection termination on Windows and resolving a significant performance regression in the queryCompiler preview feature.
6.10.0Breaking1 fix7 featuresPrisma 6.10.0 introduces Preview support for shard keys on PlanetScale and No-Rust engines for MS SQL Server, alongside significant performance boosts for Prisma Migrate and enhanced local Prisma Postgres management in VS Code.
6.9.01 fix8 featuresPrisma 6.9.0 promotes the Rust-free ORM architecture to Preview and introduces major local development enhancements for Prisma Postgres, including persistence and a new VS Code management UI.
6.8.21 fixPrisma 6.8.2 is a patch release that fully resolves execution issues with the 'init' and 'dev' commands on Windows.
6.8.11 fixPrisma 6.8.1 is a patch release that resolves critical issues with the 'init' and 'dev' commands on Windows platforms.
6.8.0Breaking4 featuresPrisma 6.8.0 introduces local development for Prisma Postgres via the 'prisma dev' command, native Deno support through a new generator, and AI-powered database workflow automation in VS Code.
6.7.0Breaking1 fix5 featuresPrisma 6.7.0 introduces an Early Access TypeScript-based Query Compiler to replace Rust engines, stabilizes multi-file schemas, and adds support for the better-sqlite3 driver adapter.
6.6.0Breaking5 featuresPrisma 6.6.0 introduces a new ESM-ready client generator, native migration support for Cloudflare D1 and Turso, and an MCP server for AI-driven database management.
6.5.0Breaking1 fix5 featuresPrisma 6.5.0 removes interactive database reset prompts in favor of explicit commands and introduces Prisma Studio support for the new prisma.config.ts configuration file.
6.4.11 fixThis patch release fixes issues with the NPS survey in the Prisma CLI, ensuring it correctly respects the --no-hints flag.
6.4.0Breaking1 fix3 featuresPrisma 6.4.0 introduces a TypeScript-based configuration file (Early Access), case-insensitive filtering for JSON data, and performance optimizations for CockroachDB migrations.
6.3.12 featuresThis patch release improves the CLI output for the 'prisma init' command and streamlines the setup process for Prisma Postgres.
6.3.03 fixes6 featuresPrisma 6.3.0 introduces a revamped Prisma Studio, adds 'limit' support to bulk update and delete operations, and improves PostgreSQL performance by switching to 'NOT EXISTS' for relation filters.
Common Errors
PrismaClientKnownRequestError12 reportsPrismaClientKnownRequestError usually indicates a problem stemming from the Prisma Client attempting an operation that violates a database constraint (like a unique constraint), or experiencing an issue with connection parameters. Fix it by carefully examining the `code` property of the error object to identify the specific issue (e.g., P2002 for unique constraint violations) and adjust your Prisma Client code and database schema/connection URL accordingly, or upgrading to the latest prisma version for bug fixes. Also ensure your database connection string includes all necessary parameters, such as the schema if relevant.
DriverAdapterError7 reportsDriverAdapterError in Prisma usually indicates a mismatch or misconfiguration between the Prisma client and the underlying database driver. Ensure your database connection string in the Prisma schema is correct, the database server is running and accessible, and that the Prisma client and adapter versions are compatible with your database version. Double-check for typos in the connection string and verify that the necessary database driver dependencies (e.g., `pg`, `mysql2`) are installed.
PrismaClientInitializationError5 reportsPrismaClientInitializationError usually stems from connection issues to your database or misconfiguration, often due to an incorrect or missing DATABASE_URL environment variable. To fix it, ensure your DATABASE_URL is correctly set in your environment and that your database server is running and accessible from your application. Double-check your Prisma schema for accuracy and consider using `npx prisma migrate dev` to ensure schema and database are in sync.
PrismaClientValidationError3 reportsThe "PrismaClientValidationError", especially around enums, often arises from mismatches between the Prisma schema's enum definitions and the data you're trying to insert (e.g., using a mapped value instead of the actual database value or providing an invalid enum value). Ensure the values passed to Prisma Client for enum fields exactly match the enum values defined in your Prisma schema and reflect the underlying database values if `@map` is not correctly configured. If using `@map`, verify Prisma's generated code correctly interprets the mapping during data creation/updates, potentially requiring schema adjustments or Prisma upgrade.
PrismaClientConstructorValidationError3 reportsThe "PrismaClientConstructorValidationError" often arises from incorrect Prisma Client initialization, especially after version upgrades. Verify that your Prisma Client constructor includes either the `adapter` option for adapter-based setups or the `accelerateUrl` option when using Prisma Accelerate, as required by your Prisma version, or for older versions, missing specific engine types altogether. Ensure the specified `engineType` in your schema and constructor options (like `client` or `binary`) is compatible and correctly configured in your `PrismaClient` constructor.
PrismaConfigEnvError2 reportsThe "PrismaConfigEnvError" usually means a required environment variable like `DATABASE_URL` is missing or not accessible to Prisma. To fix this, ensure the necessary environment variables are defined in your `.env` file or system environment and that Prisma can access them. Double-check the variable names for typos and restart your terminal or deployment environment to load the updated variables.
Related Backend & Infra Packages
Production-Grade Container Scheduling and Management
Node.js JavaScript runtime ✨🐢🚀✨
Promise based HTTP client for the browser and node.js
A modern runtime for JavaScript and TypeScript.
Deliver web apps with confidence 🚀
Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
Subscribe to Updates
Get notified when new versions are released