@prisma/client
Prisma Client is an auto-generated, type-safe and modern JavaScript/TypeScript ORM for Node.js that's tailored to your data. Supports PostgreSQL, CockroachDB, MySQL, MariaDB, SQL Server, SQLite & MongoDB databases.
About
Prisma Client is an auto-generated, type-safe and modern JavaScript/TypeScript ORM for Node.js that's tailored to your data. Supports PostgreSQL, CockroachDB, MySQL, MariaDB, SQL Server, SQLite & MongoDB databases.
What detecting @prisma/client tells you about a site
@prisma/client is the generated, type-safe runtime that application code actually imports to query the database. Its presence confirms a Prisma data layer; because it is meant to run only on the server, finding it in a browser bundle is a red flag for a leaked server import worth investigating.
Why the exact @prisma/client version matters
The client version must match the Prisma schema/CLI version that generated it; reading the exact version is also how you confirm whether the app is on a current, supported Prisma generation.
@prisma/client in a real-world stack
When you find @prisma/client in a bundle, it rarely travels alone. prisma (the CLI/toolkit that generates it), and a server framework that owns the database connection.
Quick facts
npm install @prisma/clientCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
What @prisma/client pulls in
@prisma/client declares 1 direct dependency — each one also rides into any bundle that ships @prisma/client, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .
How Sourcemap Explorer detects @prisma/client
@prisma/client ships as v7.9.1 and carries 1 direct dependency, 2 peer dependencies (prisma, typescript), 10,647 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @prisma/client rides inside a deployed bundle — here is how the detection works.
We catch @prisma/client from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@prisma/client/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `@prisma/client` paths live.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/@prisma/client/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@prisma/client/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/@prisma/client/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of @prisma/client
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the @prisma/client version a site actually ships against the ecosystem.
Recent versions
@prisma/client README
Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.
Discord | X | Blog Post | Architecture
Looking for Prisma ORM 7? It lives on the
v7branch of this repository, and theprismaand@prisma/*packages on npm continue to be published from there.
Prisma Next is currently in Early Access and we're building it in the open with the community. APIs will still evolve as your feedback shapes them, so we don't recommend it for production workloads yet. Come along for the ride: star the repo, follow @prisma on X, or read along on the Prisma blog.
Prisma Next is a TypeScript rewrite of Prisma ORM, designed to be extensible, composable, and AI-agent friendly by default. Read the full announcement: The Next Evolution of Prisma ORM.
Prerequisites
- Node.js 24 or newer
- A package manager (
npm,pnpm, oryarn)
Getting started
1. Scaffold a new project
The interactive scaffolder picks a JavaScript framework (Next.js, Vite, Hono, and others) and wires Prisma Next in with your chosen database (PostgreSQL or MongoDB):
npm create prisma@next
You finish with a runnable app, a starter contract, and the agent skills already registered.
2. Or, add Prisma Next to an existing project
Run this from your repo root:
npx prisma-next@latest init
prisma-next@latest init writes prisma-next.config.ts, scaffolds a starter contract and db.ts under src/prisma/, installs the runtime, emits the contract, and registers the agent skills. It does not touch your framework or build setup.
3. Use your AI agent for everything Prisma Next
Both installers leave a top-level prisma-next.md primer at your project root for any agent to read first. prisma-next@latest init additionally materialises one SKILL.md per workflow in two places, so different agent runtimes can find them at their expected paths:
.claude/skills/<skill-name>/SKILL.md— picked up by Claude Code.agents/skills/<skill-name>/SKILL.md— universal location for Cursor, Copilot Agent, and other runtimes
A skills-lock.json at the project root tracks which skill versions are installed. Your editor's AI assistant auto-loads the right skill when your prompt matches.
Just describe what you want. For example:
"Add a
postsmodel with a relation tousers, then write a query that loads each user's three most recent posts."
The agent loads prisma-next-contract for the schema edit and prisma-next-queries for the read, then drives the change end-to-end.
For the full catalogue and what each skill covers, see skills/README.md.
Found a bug, missing a feature, or have a question for the team?
Ask your agent. The prisma-next-feedback skill drafts a structured GitHub issue or hands you a Prisma Discord link for live Q&A. You can review and confirm before anything is submitted.
For extension authors
Prisma Next has a minimal core. Everything around it, including Postgres support itself, is built on the same public SPI that's available to any author. If you've wanted to integrate your tool, your database, or your library with Prisma, this is the way in.
A few extensions already shipping:
@internal/extension-pgvector: vector columns and similarity operators for semantic search.@internal/extension-paradedb: typed BM25 indexes with multiple tokenizers for full-text search.@internal/extension-postgis: geospatial types and queries.@cipherstash/prisma-next: searchable encryption and data-level access control.
Want to ship your own? The Authoring Prisma Next Extensions blog walks through the SPI, the layers your extension can hook into, and how the team features new extensions in the Prisma Next directory.
Supported databases
Prisma 8 carries PostgreSQL to general availability — and that is all at this stage:
- PostgreSQL — the primary target; general availability at Prisma 8
- MongoDB — early access; proves the framework works beyond SQL
- SQLite — a proof of concept today
MySQL follows later. See the roadmap for what must happen before the 8.0.0-rc.1 release.
Contributing
See CONTRIBUTING.md for setup, commands, DCO signoff, and PR expectations. For substantive changes, please open an issue first so we can give direction-fit feedback before you invest implementation time.
Security issues: follow the Private Vulnerability Reporting flow in SECURITY.md. Please do not file them as public issues.
Community
Built something with Prisma Next? Tag @prisma on X. The best community builds get a shout-out and a link here.
- Discord: Talk to us in Discord in the
prisma-nextchannel - X: @prisma
- Blog: prisma.io/blog
License
Apache 2.0. See LICENSE.
FAQ
What is @prisma/client used for?
Prisma Client is an auto-generated, type-safe and modern JavaScript/TypeScript ORM for Node.js that's tailored to your data. Supports PostgreSQL, CockroachDB, MySQL, MariaDB, SQL Server, SQLite & MongoDB databases.
How can I tell if a website is using @prisma/client?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@prisma/client` from two complementary signals: `node_modules/@prisma/client/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
How do I find out which version of @prisma/client a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `@prisma/client/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/@prisma/client/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 7.9.1, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of @prisma/client?
7.9.1, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Where can I read more?
Project homepage: https://www.prisma.io. Source code: https://github.com/prisma/prisma. Published on npm: https://www.npmjs.com/package/@prisma/client. Licensed as Apache-2.0.
Keep reading on Sourcemap Explorer
Practical guides
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for @prisma/client and report the precise version (registry latest: v7.9.1). Without sourcemaps, an import / require in the page's scripts is enough to flag it.