47,661
stars
+2
2,609
forks
296
watchers
10,963
prs
12,239
issues
275
releases
5,856
discussions
README
Docs | Discord | X | Blog Post | Architecture --- Using Prisma 7? It is maintained for eighteen months after 8.0.0 final; supported versions says what that covers. Its source lives on the v7 branch of this repository and its docs at prisma.io/docs/orm/v7. Prisma 8 is a release candidate. 8.0.0 final is expected in the next four to eight weeks. Until then a release candidate may include breaking changes, and every release ships with an upgrade recipe that the prisma-8 skill applies for you. The candidate is a complete implementation we stand behind: we treat bugs in it as urgent, and the risk you take on is a feature that is not built yet rather than churn. The feature scoreboard names every gap. New projects should start here. Existing Prisma 7 applications can migrate incrementally, and Prisma 7 stays maintained on the v7 branch for eighteen months after 8.0.0 final. Star the repo, follow @prisma on X, or read along on the Prisma blog. Prisma 8 is a TypeScript rewrite of Prisma ORM, designed to be extensible, composable, and AI-agent friendly by default. Read the announcement or start with the docs. Prerequisites - Node.js 24 or newer - A package manager (npm, pnpm, or yarn) Getting started 1. Scaffold a new project The interactive scaffolder picks an app template (Next.js, Hono, Nuxt, Astro, NestJS, SvelteKit, TanStack Start, or Elysia) and wires Prisma 8 in with your chosen database (PostgreSQL or MongoDB): bash npm create prisma You finish with a runnable app, a starter contract, and the agent skills already installed. See the create-prisma reference for every template and flag, or follow the PostgreSQL and MongoDB quickstarts. 2. Or, add Prisma 8 to an existing project Run this from your repo root: bash npx prisma orm init orm init writes prisma.config.ts, scaffolds a starter contract and db.ts under src/prisma/, installs the runtime, and emits the contract. It does not touch your framework or build setup. Then install the agent skills: bash npx prisma skills sync See the orm init and skills CLI references, or the guides for adding Prisma 8 to an existing PostgreSQL or MongoDB app. 3. Use your AI agent for everything Prisma 8 Both installers leave a top-level prisma-8.md primer at your project root for any agent to read first, and install one SKILL.md per workflow into the directories agent runtimes read: - .claude/skills//SKILL.md — Claude Code - .cursor/skills//SKILL.md — Cursor - .agents/skills//SKILL.md — universal location for Copilot Agent and other runtimes - .devin/skills//SKILL.md — Devin Skills ship inside the Prisma packages your project installs, so they always describe the version in use. Your editor's AI assistant auto-loads the right skill when your prompt matches. Just describe what you want. For example: "Add a posts model with a relation to users, then write a query that loads each user's three most recent posts." The agent loads the prisma-8 skill, opens its contract
Top issues
#1798Geolocation/Spatial types support163 comments · 2020-03-10#9184`EPERM: operation not permitted, unlink '...node_modules\prisma\query_engine-windows.dll.node'`156 comments · 2021-09-09#4807Large schemas generate huge `index.d.ts` causing slow autocomplete and type-checking in your editor157 comments · 2020-12-29#2443Multiple Connections / Databases / Datasources144 comments · 2020-05-14#2789PostGIS/GIS support136 comments · 2020-06-17#5051Improve Timezone Support for Existing MySQL Databases configured with a Non-UTC Timezone135 comments · 2020-06-20#3219Define type of content of `Json` field131 comments · 2020-08-06#1644Support for Polymorphic Associations126 comments · 2020-02-19
Discussions
#30954How `@updateAt` should work when used in relationships1 comments · 2026-11-06#30948Prisma 7.9.1: Can migrate deploy/diff initialize PostgreSQL SET ROLE on every engine connection?2 comments · 2026-11-05#30910Prisma 6.19.3 query engine download returns HTTP 403 (debian-openssl-3.0.x)1 comments · 2026-10-29#30908binaryTargets equivalent with @prisma/engines?3 comments · 2026-10-29#30905ES5 support on 7?2 comments · 2026-10-29#30890Prisma 7.10.0 MySQL migrate status: Minimum Required Database Privileges3 comments · 2026-10-28#30879Prisma 7.10.1 Schema Engine returns P1001 on Windows, but PostgreSQL driver connects successfully4 comments · 2026-10-27#30715Offline verification of Prisma 7.10.0 Linux schema-engine signatures3 comments · 2026-10-13
Latest release
7.10.1 7.10.1 2026-10-19Prisma ORM 7.10.1 is a patch release. It fixes a bug where a nested interactive transaction could make later, unrelated transactions run inside the wrong transaction. It also updates dependencies that had security advisories. Fixes Prisma Client: nested $transaction no longer changes the options object you pass in If you passed the same options object to a nested tx.$transaction(...) and later to a top-level prisma.$transaction(...), the nested call wrote the outer transaction's id into that object. Every later top-level transaction that used the object was then treated as nested inside t