Docs for Prisma ORM v6.16.0 #7096
Conversation
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
WalkthroughDocs updated to document Prisma ORM's Rust‑free mode (GA notes v6.15.0+/v6.16.0): generator examples now use provider = "prisma-client-js" (or "prisma-client"), often include output and engineType = "client"; driver‑adapter guidance, links, and a PostgreSQL‑extensions migration workflow were revised; preview badges/preview lists were removed or adjusted. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor Dev as Developer
participant Schema as schema.prisma
participant CLI as Prisma CLI
participant App as Application
participant Adapter as Driver Adapter
participant DB as Database
Note over Dev,Schema: Configure Prisma Client for Rust‑free mode (v6.15+/v6.16.0)
Dev->>Schema: set generator:\nprovider = "prisma-client-js" / "prisma-client"\noutput = "../src/generated/prisma"\nengineType = "client"
Dev->>CLI: npx prisma generate
CLI->>App: emit JS-only Prisma Client (no Rust engine)
Dev->>App: install & import appropriate driver adapter
App->>Adapter: instantiate adapter (e.g. new PrismaPg(...))
App->>App: new PrismaClient({ adapter })
App->>DB: queries via native driver pool
DB-->>App: results
sequenceDiagram
autonumber
actor Dev as Developer
participant CLI as Prisma CLI
participant FS as migrations/
participant DB as PostgreSQL
participant Client as Prisma Client
Note over Dev,CLI: Install PostgreSQL extension via migration
Dev->>CLI: prisma migrate dev --create-only
CLI->>FS: create empty migration file
Dev->>FS: add SQL: CREATE EXTENSION IF NOT EXISTS citext;
Dev->>CLI: prisma migrate deploy
CLI->>DB: apply migration (install extension)
Dev->>Client: use extension in Prisma Client (Unsupported fallback if needed)
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested reviewers
Pre-merge checks (3 passed)✅ Passed checks (3 passed)
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. ✨ Finishing Touches🧪 Generate unit tests
Comment |
Deploying docs with
|
| Latest commit: |
506d54c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0c446c9c.docs-51g.pages.dev |
| Branch Preview URL: | https://docs-6-16-0.docs-51g.pages.dev |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 15
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (7)
content/800-guides/240-management-api.mdx (1)
63-87: Remove merge conflict markers and unify token placeholder
The Step 3 snippet still contains<<<<<<<,=======,>>>>>>>markers and uses<YOUR_INTEGRATION_TOKEN>. Replace the entire conflicted block with the code block using<YOUR_SERVICE_TOKEN>to match Step 2, for example:-<<<<<<< HEAD - -```ts -const prismaResponse = await fetch('https://api.prisma.io/v1/projects', { - method: 'POST', - headers: { - 'Content-Type': 'application/json', - Authorization: `Bearer <YOUR_SERVICE_TOKEN>`, - }, - body: JSON.stringify({ region, name }), -}); -``` - -======= - ```ts - const prismaResponse = await fetch('https://api.prisma.io/v1/projects', { - method: 'POST', - headers: { - 'Content-Type': 'application/json', - Authorization: `Bearer <YOUR_INTEGRATION_TOKEN>`, - }, - body: JSON.stringify({ region, name }), - }); - ``` ->>>>>>> 12ea903475c19dd28e7551929132fe9ca9aac600 +```ts +const prismaResponse = await fetch('https://api.prisma.io/v1/projects', { + method: 'POST', + headers: { + 'Content-Type': 'application/json', + Authorization: `Bearer <YOUR_SERVICE_TOKEN>`, + }, + body: JSON.stringify({ region, name }), +}); +```Then verify no remaining
<YOUR_INTEGRATION_TOKEN>placeholders in the file.content/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdx (2)
15-35: Update “Use Prisma ORM without Rust binaries” to GA flow (engineType="client").Replace previewFeatures guidance with engineType="client" + adapters.
-:::tip Use Prisma ORM without Rust binaries - -If Prisma’s Rust engine binaries cause large bundle sizes, slow builds, or deployment issues (for example, in serverless or edge environments), you can switch to the [`queryCompiler`](/orm/prisma-client/setup-and-configuration/no-rust-engine) Preview feature introduced in [v6.7.0](https://pris.ly/release/6.7.0). - -**When enabled, Prisma Client is generated without a Rust-based query engine binary**, reducing build artifacts and removing native binary dependencies: - -```prisma -generator client { - provider = "prisma-client-js" - previewFeatures = ["queryCompiler", "driverAdapters"] -} -``` - -Note that the [`driverAdapters`](/orm/overview/databases/database-drivers#driver-adapters) Preview feature is **required** alongside `queryCompiler`. -When using this architecture: +:::tip Use Prisma ORM without Rust binaries + +As of [v6.15.0](https://pris.ly/release/6.15.0), you can use Prisma ORM without Rust engines in production. **Prisma Client is generated without a Rust-based query engine binary**, reducing build artifacts and removing native binary dependencies: + +```prisma +generator client { + provider = "prisma-client-js" // or "prisma-client" + output = "./generated/client" + engineType = "client" // no Rust engine +} +``` + +Note that [driver adapters](/orm/overview/databases/database-drivers#driver-adapters) are required when using Prisma ORM without Rust engines. +When using this architecture: @@ -This setup can simplify deployments in serverless or edge runtimes. Learn more in the [docs here](/orm/prisma-client/setup-and-configuration/no-rust-engine). Curious why we're moving away from the Rust engine? Take a look at why we're transitioning from Rust binary engines to an all-TypeScript approach for a faster, lighter Prisma ORM in our [blog post](https://www.prisma.io/blog/try-the-new-rust-free-version-of-prisma-orm-early-access). +This setup can simplify deployments in serverless or edge runtimes. Learn more in the [docs here](/orm/prisma-client/setup-and-configuration/no-rust-engine). Read about performance/DX improvements in [this blog post](https://www.prisma.io/blog/prisma-orm-without-rust-latest-performance-benchmarks). :::
87-93: Make JSON valid: add missing colon after "scripts".- "scripts" { + "scripts": {content/200-orm/800-more/100-under-the-hood/100-engines.mdx (1)
236-244: Include new engineType value “client” in the valid values and description.The page uses engineType="client" above; list it as a valid option here and clarify semantics.
-Valid values for `engineType` are `binary` and `library`. You can also use the environment variable [`PRISMA_CLIENT_ENGINE_TYPE`](/orm/reference/environment-variables-reference#prisma_client_engine_type) instead. +Valid values for `engineType` are `client`, `library`, and `binary`: +- `client`: uses the Rust-free client engine (JS/TS) with a driver adapter. +- `library`: loads the Rust query engine as a Node-API library. +- `binary`: runs the Rust query engine as a separate process. +You can also use the environment variable [`PRISMA_CLIENT_ENGINE_TYPE`](/orm/reference/environment-variables-reference#prisma_client_engine_type) instead.content/200-orm/050-overview/500-databases/200-database-drivers.mdx (3)
4-4: Remove “(Preview)” from metaDescription (driver adapters are GA).-metaDescription: 'Learn how Prisma connects to your database using the built-in drivers and how you can use Prisma along with other JavaScript database drivers using driver adapters (Preview)' +metaDescription: 'Learn how Prisma connects to your database using built-in drivers and how you can use Prisma with other JavaScript database drivers using driver adapters.'
81-90: Update “How to use driver adapters” to GA (no previewFeatures needed).-1. Update the `previewFeatures` block in your schema to include the `driverAdapters` Preview feature: - ```prisma - generator client { - provider = "prisma-client-js" - previewFeatures = ["driverAdapters"] - } - ``` +1. Install the adapter package for your driver (example for PostgreSQL with `pg`): + ```terminal + npm i @prisma/adapter-pg pg + ``` +2. Ensure your Prisma Client is generated (no previewFeatures needed): + ```terminal + npx prisma generate + ```
138-138: Fix incorrect import path for PrismaClient in 6.6.0+ example.-import { PrismaClient } from '../prisma/prisma-client' +import { PrismaClient } from '@prisma/client'
🧹 Nitpick comments (17)
content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx (1)
27-28: Replace placeholder feedback links with correct targets (or remove if none).Both rows point to the generic issues root; please use concrete issue/discussion IDs.
content/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdx (1)
83-83: Fix spelling: “additonally” → “additionally”.-In a more sophisticated CI/CD environment, you may additonally want to update the database schema +In a more sophisticated CI/CD environment, you may additionally want to update the database schemacontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx (4)
13-13: Fix subject-verb agreement (MongoDB connector).Use singular “connector uses”.
-Relational database connectors use Prisma ORM's own connection pool, and the MongoDB connectors uses the ... +Relational database connectors use Prisma ORM's own connection pool, and the MongoDB connector uses the ...
29-31: Clarify pool configuration with driver adapters.Add a link or brief note on how to set pool size/timeouts via each adapter/driver to reduce confusion.
49-51: Grammar: timeout sentence and stray space.Tighten wording and remove extra space before period.
-If the query engine cannot process a query in the queue for **before the [time limit](#default-pool-timeout)**, it throws an exception ... -If you consistently experience pool timeout errors, you need to [optimize the connection pool](/orm/prisma-client/setup-and-configuration/databases-connections#optimizing-the-connection-pool) . +If the query engine cannot process a query in the queue **before the [time limit](#default-pool-timeout)**, it throws an exception ... +If you consistently experience pool timeout errors, you need to [optimize the connection pool](/orm/prisma-client/setup-and-configuration/databases-connections#optimizing-the-connection-pool).
121-121: Pluralization.“connections” (plural).
-... the amount of in-use and idle connection, you can use the ... +... the amount of in-use and idle connections, you can use the ...content/200-orm/200-prisma-client/500-deployment/700-deploy-to-a-different-os.mdx (1)
30-36: Scope the binaryTargets guidance to Rust-engine users.Add an info note that binaryTargets applies only when using Rust engines; with engineType="client" this section can be skipped.
The binary is downloaded when `prisma generate` is called. +<Admonition type="info"> +If you use Prisma ORM without Rust engines (`engineType = "client"`), you do not need to configure `binaryTargets` and can skip the steps below. +</Admonition>content/200-orm/200-prisma-client/500-deployment/400-module-bundlers.mdx (1)
11-12: Call out skip-path for no-Rust-engine users.Explicitly state that copying the query engine binary is unnecessary with
engineType="client".-Since Prisma Client is not only based on JavaScript code, but also relies on the [**query engine binary file**](/orm/more/under-the-hood/engines#the-query-engine-file) to be available, you need to make sure that your bundled code has access to the binary file. +Since Prisma Client relies on the [**query engine binary file**](/orm/more/under-the-hood/engines#the-query-engine-file) when using Rust engines, you must ensure your bundle has access to it. +If you generate without Rust engines (`engineType = "client"`), you can skip copying engine assets.content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx (2)
38-39: Remove duplicate word.“the number” (single “the”).
-`num_physical_cpus` refers to the the number of CPUs of the machine your application is running on. +`num_physical_cpus` refers to the number of CPUs of the machine your application is running on.
204-212: Fix Promise.all example.Use array form and valid syntax.
-```ts -Promise.all() { - query1, - query2, - query3 - query4, - ... -} -``` +```ts +await Promise.all([ + query1, + query2, + query3, + query4, + // ... +]) +```content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (4)
15-16: Fix duplicate words.Remove “on the”.
-- `engineType = "client"` field needs to be set on the on the `generator` block +- `engineType = "client"` field needs to be set on the `generator` block
38-42: Grammar: add “to”.-To make the configuration take effect, you need re-generate Prisma Client: +To make the configuration take effect, you need to re-generate Prisma Client:
96-158: Import path consistency with customoutput.Examples mix
@prisma/clientand./generated/prismawhile generator setsoutput = "../generated/prisma". Standardize or add a note clarifying imports change whenoutputis set.-Import { PrismaClient } from '@prisma/client' +// If you set a custom output in generator, import from that path: +// import { PrismaClient } from './generated/prisma' +// Otherwise, use the default: +// import { PrismaClient } from '@prisma/client'Also applies to: 186-205
214-417: Preview section: same grammar and Neon label fixes.Apply “need to re-generate” and ensure “Neon Serverless” spelling in TabItem.
-To make the feature flags take effect, you need re-generate Prisma Client: +To make the feature flags take effect, you need to re-generate Prisma Client: ... -<TabItem value="Neon Serverles"> +<TabItem value="Neon Serverless">content/200-orm/200-prisma-client/500-deployment/650-caveats-when-deploying-to-aws-platforms.mdx (1)
81-84: Clarify deletion guidance below for no-Rust users.Consider adding a one-liner here that the “Deleting Prisma ORM engines” section applies only when using Rust engines, since no-Rust users won’t have engine binaries to strip. (prisma.io)
content/200-orm/100-prisma-schema/10-overview/03-generators.mdx (2)
101-103: Grammar nit: “anymore” (adverb), not “any more”.-- Requires an `output` path; no "magic" generation into `node_modules` any more +- Requires an `output` path; no "magic" generation into `node_modules` anymore
107-107: Grammar fix: missing conjunction.-The `prisma-client` generator has been Generally Available since [v6.15.0](https://pris.ly/releases/6.15.0) will become the new default with Prisma ORM v7. +The `prisma-client` generator has been Generally Available since [v6.15.0](https://pris.ly/releases/6.15.0) and will become the new default with Prisma ORM v7.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (14)
content/200-orm/050-overview/500-databases/200-database-drivers.mdx(1 hunks)content/200-orm/100-prisma-schema/10-overview/03-generators.mdx(4 hunks)content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx(1 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx(1 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx(1 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx(2 hunks)content/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdx(1 hunks)content/200-orm/200-prisma-client/500-deployment/400-module-bundlers.mdx(1 hunks)content/200-orm/200-prisma-client/500-deployment/650-caveats-when-deploying-to-aws-platforms.mdx(1 hunks)content/200-orm/200-prisma-client/500-deployment/700-deploy-to-a-different-os.mdx(1 hunks)content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx(2 hunks)content/200-orm/800-more/100-under-the-hood/100-engines.mdx(1 hunks)content/250-postgres/100-introduction/230-management-api.mdx(1 hunks)content/800-guides/240-management-api.mdx(2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
📚 Learning: 2025-08-11T09:40:55.237Z
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
Applied to files:
content/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdxcontent/200-orm/200-prisma-client/500-deployment/700-deploy-to-a-different-os.mdxcontent/200-orm/800-more/100-under-the-hood/100-engines.mdxcontent/200-orm/200-prisma-client/500-deployment/400-module-bundlers.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdxcontent/200-orm/200-prisma-client/500-deployment/650-caveats-when-deploying-to-aws-platforms.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/200-orm/100-prisma-schema/10-overview/03-generators.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdx
🪛 LanguageTool
content/250-postgres/100-introduction/230-management-api.mdx
[grammar] ~62-~62: There might be a mistake here.
Context: ... location for future use. <<<<<<< HEAD #### Creating OAuth credentials ======= #### ...
(QB_NEW_EN)
[grammar] ~63-~63: There might be a mistake here.
Context: ...<<< HEAD #### Creating OAuth credentials ======= #### Creating an OAuth credentia...
(QB_NEW_EN)
[grammar] ~64-~64: There might be a mistake here.
Context: ... #### Creating OAuth credentials ======= #### Creating an OAuth credentials >>>>>>> 12...
(QB_NEW_EN)
[grammar] ~65-~65: There might be a mistake here.
Context: ...===== #### Creating an OAuth credentials >>>>>>> 12ea903...
(QB_NEW_EN)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
[grammar] ~15-~15: There might be a mistake here.
Context: ... "client"field needs to be set on the on thegeneratorblock - nobinaryTargets` ...
(QB_NEW_EN)
[grammar] ~101-~101: There might be a mistake here.
Context: ...ctionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
[grammar] ~119-~119: There might be a mistake here.
Context: ...isma/adapter-d1' export interface Env { DB: D1Database } export default { asy...
(QB_NEW_EN)
[grammar] ~156-~156: There might be a mistake here.
Context: ....env.DATABASE_URL, fetch: undiciFetch }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
[grammar] ~190-~190: There might be a mistake here.
Context: ...ctionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
content/200-orm/100-prisma-schema/10-overview/03-generators.mdx
[uncategorized] ~101-~101: Did you mean the adverb “anymore”?
Context: ... "magic" generation into node_modules any more - Doesn't load .env at runtime; use `...
(ANY_MORE)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: runner / linkspector
🔇 Additional comments (5)
content/200-orm/200-prisma-client/500-deployment/650-caveats-when-deploying-to-aws-platforms.mdx (2)
69-72: Version claim: please verify GA/version wording.Docs currently state “No Rust engine” was introduced in v6.7.0 (later GA status may differ). If you intend to communicate GA in v6.15.0, please confirm in release notes and adjust phrasing to avoid confusion. For example: “Introduced in v6.7.0, GA in v6.15.0 …”. (prisma.io)
81-84: Driver adapters note looks good.Clear and correctly linked for the no-Rust path.
content/200-orm/100-prisma-schema/10-overview/03-generators.mdx (3)
48-49: Confirm GA/version statement.If you’re asserting GA “as of v6.15.0”, please verify and align with the “No Rust engine” page and release notes, which still anchor the feature’s introduction to v6.7.0. Adjust wording if needed (e.g., “Introduced in 6.7.0, GA in 6.15.0”). (prisma.io, newreleases.io)
60-66: These two notes are accurate for no-Rust.
- Driver adapters required.
- binaryTargets obsolete.
144-146: Fence change to “terminal” looks fine.No issues with the code block update.
content/200-orm/100-prisma-schema/10-overview/03-generators.mdx
Outdated
Show resolved
Hide resolved
...-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx
Outdated
Show resolved
Hide resolved
...nt/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx
Outdated
Show resolved
Hide resolved
content/200-orm/200-prisma-client/500-deployment/700-deploy-to-a-different-os.mdx
Outdated
Show resolved
Hide resolved
content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx
Outdated
Show resolved
Hide resolved
content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx
Outdated
Show resolved
Hide resolved
content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx
Outdated
Show resolved
Hide resolved
Dangerous URL checkNo absolute URLs to prisma.io/docs found. |
Redirect checkThis PR probably requires the following redirects to be added to static/_redirects:
|
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
…300-no-rust-engine.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 4
♻️ Duplicate comments (1)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (1)
281-285: Typo: “Neon Serverles”.-<TabItem value="Neon Serverles"> +<TabItem value="Neon Serverless">
🧹 Nitpick comments (5)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (2)
15-16: Grammar: remove duplicated words.-- `engineType = "client"` field needs to be set on the on the `generator` block +- `engineType = "client"` field needs to be set on the `generator` block
38-42: Grammar: “need to regenerate.”-To make the configuration take effect, you need re-generate Prisma Client: +To make the configuration take effect, you need to regenerate Prisma Client:content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx (3)
44-48: Grammar: tiny tweak.-Run the following command to deploy the migration and apply to your database: +Run the following command to deploy the migration and apply it to your database:
50-52: Heading trailing space.-### 4. Use the extension +### 4. Use the extension
22-52: Optional: mention required privileges.Consider adding a note that the database role must have CREATE EXTENSION privileges (and that some managed DBs restrict which extensions are available).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (2)
content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx(1 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx(2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
📚 Learning: 2025-08-11T09:40:55.237Z
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
Applied to files:
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
🪛 LanguageTool
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
[grammar] ~15-~15: There might be a mistake here.
Context: ... "client"field needs to be set on the on thegeneratorblock - nobinaryTargets` ...
(QB_NEW_EN)
[grammar] ~96-~96: There might be a mistake here.
Context: ...ctionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
[grammar] ~114-~114: There might be a mistake here.
Context: ...isma/adapter-d1' export interface Env { DB: D1Database } export default { asy...
(QB_NEW_EN)
[grammar] ~151-~151: There might be a mistake here.
Context: ....env.DATABASE_URL, fetch: undiciFetch }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
[grammar] ~185-~185: There might be a mistake here.
Context: ...ctionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
🪛 GitHub Actions: Check all content (MDX) links
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
[error] 84-84: MDX compilation failed: Expected a closing tag for (84:1-84:34).
🪛 GitHub Actions: Lost Pixel
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
[error] 84-84: MDX compilation failed during npm run build. Expected a closing tag for (84:1-84:34).
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: runner / linkspector
🔇 Additional comments (3)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (1)
7-8: Version reference: confirm 6.15.0 vs 6.16.0 phrasing.This page is under a v6.16.0 docs PR but states GA “As of v6.15.0”. Likely correct historically, but please confirm this wording is what we want for the 6.16.0 release notes/docs context.
content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx (2)
3-5: Meta fields update looks good.
10-14: Correct flag name and deprecation wording look accurate.
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
Outdated
Show resolved
Hide resolved
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
Outdated
Show resolved
Hide resolved
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
Outdated
Show resolved
Hide resolved
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
Outdated
Show resolved
Hide resolved
…300-no-rust-engine.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 6
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (3)
content/200-orm/100-prisma-schema/10-overview/03-generators.mdx (1)
144-149: Clarify binary generation based on engine mode.This sentence is inaccurate for no‑Rust mode; adjust to cover both cases.
-This generates the code for Prisma Client (including the query engine binary) into the specified `output` folder. +This generates the code for Prisma Client into the specified `output` folder. +If you’re using Rust engines, the query engine binary is included. In no‑Rust mode, no binary is generated.content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (2)
193-413: Fix MDX structure causing build failure.The MDX structure is malformed with an unexpected closing
</details>tag without proper TabItem closure, causing the build to fail.Based on the pipeline error, there's a structural issue in the MDX. The Neon Serverless TabItem needs proper closure before the details section ends:
const adapter = new PrismaNeon({ connectionString }) const prisma = new PrismaClient({ adapter }) +``` </TabItem> </TabbedContent> ### 5. Query your database If you went through the previous steps, you can query your database as you're used to with Prisma Client. No other changes are needed. </details>
283-283: Typo in TabItem value: "Neon Serverles".There's a typo in the Neon Serverless tab label within the older versions section.
-<TabItem value="Neon Serverles"> +<TabItem value="Neon Serverless">
♻️ Duplicate comments (6)
content/200-orm/200-prisma-client/500-deployment/650-caveats-when-deploying-to-aws-platforms.mdx (1)
75-78: engineType = "client" is invalid in schema; omit engineType for Rust‑free.Valid values are “binary” or “library”. The Rust‑free flow requires no engineType or binaryTargets on the generator. Remove the line. (prisma.io)
Apply:
generator client { - provider = "prisma-client-js" // or "prisma-client" - output = "../src/generated/prisma" - engineType = "client" // no Rust engine + provider = "prisma-client-js" // or "prisma-client" + output = "../src/generated/prisma" }content/200-orm/200-prisma-client/500-deployment/400-module-bundlers.mdx (1)
21-23: Clarifyproviderchoices and preview status in the snippet.Add a brief inline note that
prisma-clientis the new ESM‑friendly generator in Preview (v6.x) and requiresoutput, whileprisma-client-jskeeps its default location. This mirrors current generator docs. (prisma.io)generator client { - provider = "prisma-client-js" // or "prisma-client" - output = "../src/generated/prisma" + provider = "prisma-client-js" // or "prisma-client" (Preview; requires `output`) + output = "../src/generated/prisma" // required for `prisma-client`; optional for `prisma-client-js` engineType = "client" // no Rust engine }content/200-orm/100-prisma-schema/10-overview/03-generators.mdx (2)
107-107: Grammar fix: missing conjunction.Add “and”.
-The `prisma-client` generator has been Generally Available since [v6.16.0](https://pris.ly/releases/6.16.0) will become the new default with Prisma ORM v7. +The `prisma-client` generator has been Generally Available since [v6.16.0](https://pris.ly/releases/6.16.0) and will become the new default with Prisma ORM v7.
48-58: Incorrect no‑Rust snippet: removeengineType; keepprovider/outputonly.In the no‑Rust flow,
engineTypeisn’t used. Showing it here is misleading.Apply:
generator client { - provider = "prisma-client-js" // or "prisma-client" - output = "../src/generated/prisma" - engineType = "client" // no Rust engine + provider = "prisma-client-js" // or "prisma-client" + output = "../src/generated/prisma" }content/200-orm/050-overview/500-databases/890-neon.mdx (1)
11-13: Fix broken TOC anchor for GA section (remove “-preview”).The H2 no longer has “(Preview)”, but the TOC link still points to the old anchor, which will 404.
-- [Use Neon's serverless driver with Prisma ORM](#how-to-use-neons-serverless-driver-with-prisma-orm-preview) +- [Use Neon's serverless driver with Prisma ORM](#how-to-use-neons-serverless-driver-with-prisma-orm)content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (1)
48-89: Update adapter package names to match official packages.The adapter package names and supported databases list should be updated to use the official Prisma v6 packages as identified in previous reviews.
Based on previous review feedback, the adapter packages and GA-supported databases need to be updated to match the official Prisma v6 packages. This includes using the correct package names like
@prisma/adapter-pg,@prisma/adapter-mariadb, etc., and ensuring the GA-supported database list matches the current documentation.
🧹 Nitpick comments (14)
content/200-orm/200-prisma-client/500-deployment/650-caveats-when-deploying-to-aws-platforms.mdx (4)
81-82: Driver adapters are required—add a 2‑line usage hint.Including a minimal example avoids confusion at deploy time. (prisma.io)
Append after the note:
+For example (PostgreSQL): +`npm i @prisma/adapter-pg` then: +```ts +import { PrismaClient } from '../src/generated/prisma' +import { PrismaPg } from '@prisma/adapter-pg' +const prisma = new PrismaClient({ adapter: new PrismaPg({ connectionString: process.env.DATABASE_URL! }) }) +```Also consider adding a short tip that, when using Rust‑free, the “Deleting Prisma ORM engines” section below can be skipped.
+:::tip +If you’re using Prisma ORM without Rust engines, you can skip the “Deleting Prisma ORM engines that are not required” section below. +:::
83-84: Ensure the performance blog link matches the current release stage.The linked post currently frames Rust‑free as Preview; if this PR promotes GA, link to the latest GA announcement instead (or add a sentence clarifying GA). (prisma.io)
62-63: Grammar: “a deployment package upload limit.”Change “an deployment” → “a deployment”.
-AWS Lambda defines an deployment package upload limit, which includes: +AWS Lambda defines a deployment package upload limit, which includes:
49-56: Offer a secure alternative tosslmode=no-verifyfor RDS.Keep the quick‑fix, but add a secure example using
sslmode=verify-fullwith the RDS CA bundle viasslrootcert. This is the recommended production setup. (docs.aws.amazon.com)Add after the “Why This Works” section:
+### Production‑grade SSL (recommended) +Instead of `sslmode=no-verify`, supply the RDS CA bundle and use strict verification: +```bash +# Download the RDS certificate bundle (global-bundle.pem) and reference it: +DATABASE_URL='postgresql://<username>:<password>@<host>/<database>?sslmode=verify-full&sslrootcert=/path/global-bundle.pem&schema=public' +``` +This verifies the server certificate while keeping the connection encrypted.content/200-orm/200-prisma-client/500-deployment/400-module-bundlers.mdx (4)
15-18: Confirm GA status and tighten wording of the callout header.
- Current public docs still describe the Rust‑free path as Preview with feature flags and explicitly say there’s no
engineType/binaryTargetsin that mode. Please double‑check that v6.16.0 is GA and thatengineType = "client"is the intended configuration before this lands, and ensure the linked “No Rust engine” page is updated in the same PR to avoid cross‑page contradictions. (prisma.io)- Minor copy edit improves clarity.
-**When enabled, your Prisma Client will be generated without a Rust-based query engine binary**: +**When Rust‑free mode is enabled, Prisma Client is generated without a Rust‑based query engine binary:**
27-27: Link to adapter guidance and scope.Good to call out adapters. Consider linking directly to the adapters overview so readers can pick the right one per database. The adapters requirement is explicitly called out for the Rust‑free path. (prisma.io)
29-30: Ensure the blog post aligns with GA wording.The linked benchmark post currently frames Rust‑free as “in Preview”. If this page states GA in v6.16.0, verify that the blog title/intro won’t confuse readers or add a brief “benchmarks from the Preview phase” qualifier. (prisma.io)
15-30: Make the bundler guidance conditional.Right after the callout, readers may assume they always need to copy a binary. Suggest adding a one‑liner before the plugins table clarifying that copying the query engine applies only when using Rust engines; Rust‑free mode (this section) does not require copying a binary.
Proposed addition (outside the changed lines, just above Line 33):
If you’re using the Rust‑based engines, you must copy the query engine binary with your bundle. If you’re using Rust‑free mode (as shown above), the binary copy step is not required.content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx (2)
24-24: Replace placeholder feedback link for shardKeys.Current link targets the generic issues page.
-| `shardKeys` | [6.10.0](https://pris.ly/release/6.10.0) | [Submit feedback](https://github.com/prisma/prisma/issues/) | +| `shardKeys` | [6.10.0](https://pris.ly/release/6.10.0) | [Submit feedback](https://github.com/prisma/prisma/issues/3108) |If there’s a dedicated tracking issue/discussion for shardKeys, link that instead of 3108.
17-17: Mark metrics as deprecated in the Preview list (matches release notes).Optional labelling to reduce confusion until removal in v7.
-| [`metrics`](/orm/prisma-client/observability-and-logging/metrics) | [3.15.0](https://github.com/prisma/prisma/releases/tag/3.15.0) | [Submit feedback](https://github.com/prisma/prisma/issues/13579) | +| [`metrics`](/orm/prisma-client/observability-and-logging/metrics) (deprecated) | [3.15.0](https://github.com/prisma/prisma/releases/tag/3.15.0) | [Submit feedback](https://github.com/prisma/prisma/issues/13579) |Release notes flag the Metrics preview feature as deprecated (pending removal in Prisma 7). (github.com)
content/200-orm/100-prisma-schema/10-overview/03-generators.mdx (1)
101-101: Grammar nit: “any more” → “anymore”.Minor polish for consistency.
-- Requires an `output` path; no "magic" generation into `node_modules` any more +- Requires an `output` path; no "magic" generation into `node_modules` anymorecontent/200-orm/050-overview/500-databases/890-neon.mdx (3)
115-116: Nit: remove stray space before period.There’s an extra space before the period after the “driver adapter” link.
-You can use Prisma ORM along with the Neon serverless driver using a [driver adapter](/orm/overview/databases/database-drivers#driver-adapters) . +You can use Prisma ORM along with the Neon serverless driver using a [driver adapter](/orm/overview/databases/database-drivers#driver-adapters).
123-127: Typo: “istall” → “install”.Fix spelling in the setup step.
-To get started, istall the Prisma ORM adapter for Neon: +To get started, install the Prisma ORM adapter for Neon:
129-141: PrismaNeon instantiation is correct; add optional pooling guidance and remove cache tip
- The snippet
new PrismaNeon({ connectionString })matches the official Prisma docs and requires no change.- For serverless/edge workloads issuing multiple queries or transactions, consider creating and passing a
Pool/Clientfrom@neondatabase/serverless(or use theneon(...)helper for single-shot queries) to improve reliability and latency.- Remove any
neonConfig.fetchConnectionCachenotes—server-side connection caching is now built-in and the experimental opt-in has been removed.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (11)
content/200-orm/050-overview/500-databases/890-neon.mdx(1 hunks)content/200-orm/100-prisma-schema/10-overview/03-generators.mdx(6 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx(1 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx(1 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx(2 hunks)content/200-orm/200-prisma-client/500-deployment/400-module-bundlers.mdx(1 hunks)content/200-orm/200-prisma-client/500-deployment/650-caveats-when-deploying-to-aws-platforms.mdx(1 hunks)content/200-orm/200-prisma-client/500-deployment/700-deploy-to-a-different-os.mdx(1 hunks)content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx(2 hunks)content/200-orm/800-more/100-under-the-hood/100-engines.mdx(1 hunks)content/800-guides/240-management-api.mdx(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (5)
- content/200-orm/200-prisma-client/500-deployment/700-deploy-to-a-different-os.mdx
- content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx
- content/200-orm/800-more/100-under-the-hood/100-engines.mdx
- content/800-guides/240-management-api.mdx
- content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
📚 Learning: 2025-08-11T09:40:55.237Z
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
Applied to files:
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdxcontent/200-orm/200-prisma-client/500-deployment/650-caveats-when-deploying-to-aws-platforms.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/200-orm/200-prisma-client/500-deployment/400-module-bundlers.mdxcontent/200-orm/100-prisma-schema/10-overview/03-generators.mdx
🪛 LanguageTool
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
[grammar] ~15-~15: There might be a mistake here.
Context: ... "client"field needs to be set on the on thegeneratorblock - nobinaryTargets` ...
(QB_NEW_EN)
[grammar] ~101-~101: There might be a mistake here.
Context: ...ctionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
[grammar] ~119-~119: There might be a mistake here.
Context: ...isma/adapter-d1' export interface Env { DB: D1Database } export default { asy...
(QB_NEW_EN)
[grammar] ~156-~156: There might be a mistake here.
Context: ....env.DATABASE_URL, fetch: undiciFetch }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
[grammar] ~157-~157: There might be a mistake here.
Context: ...t prisma = new PrismaClient({ adapter }) ```ty...
(QB_NEW_EN)
[grammar] ~189-~189: There might be a mistake here.
Context: ...ctionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
content/200-orm/050-overview/500-databases/890-neon.mdx
[grammar] ~123-~123: Ensure spelling is correct
Context: .../release/6.16.0). ::: To get started, istall the Prisma ORM adapter for Neon: ```te...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
content/200-orm/100-prisma-schema/10-overview/03-generators.mdx
[uncategorized] ~101-~101: Did you mean the adverb “anymore”?
Context: ... "magic" generation into node_modules any more - Doesn't load .env at runtime; use `...
(ANY_MORE)
[grammar] ~215-~215: There might be a mistake here.
Context: ... | | ------------------------ | -----------...
(QB_NEW_EN)
[grammar] ~216-~216: There might be a mistake here.
Context: ...-------------------------------------- | | output (required) | ...
(QB_NEW_EN)
[style] ~221-~221: To form a complete sentence, be sure to include a subject.
Context: ...xtension used in import statements. Can be ts, mts, cts, js, mjs, `cj...
(MISSING_IT_THERE)
🪛 GitHub Actions: Check all content (MDX) links
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
[error] 412-412: Command failed: npm run clean && npm run build. MDX compilation failed: Unexpected closing tag
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: runner / linkspector
- GitHub Check: Lost Pixel
🔇 Additional comments (8)
content/200-orm/200-prisma-client/500-deployment/650-caveats-when-deploying-to-aws-platforms.mdx (1)
69-72: Confirm release stage and wording for “no Rust engines” in v6.16.0.Public sources show Rust‑free is available since v6.7.0 and remained in Preview as of v6.9.0. Please verify GA/production status for 6.16.0 and adjust phrasing if needed (e.g., “available” vs. “GA/production”). (prisma.io)
If still not GA: consider “As of v6.16.0, you can use Prisma ORM without Rust engines. See …” (omit “in production applications”).
content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx (1)
55-55: Double‑check driverAdapters GA version (6.16.0 vs 6.15.0).Recent comms focus GA in September 2025 together with Query Compiler; confirm this row’s GA version before merge. If GA actually landed in 6.15.0, adjust accordingly; if it’s 6.16.0, keep as-is.
Evidence pointing to Sep 2025 GA window and driverAdapters merging into Query Compiler. (github.com)
content/200-orm/100-prisma-schema/10-overview/03-generators.mdx (2)
20-20: Good clarification on the recommended generator.Accurately calls out that
prisma-clientoutputs plain TS and requires a customoutputpath.
60-63: Clear, actionable guidance for no‑Rust mode.Calling out driver adapters and noting
binaryTargetsis obsolete without Rust is correct.content/200-orm/050-overview/500-databases/890-neon.mdx (2)
111-111: Good: GA heading updated.Dropping “(Preview)” in the section title aligns with the GA status.
151-155: Resolved: Theschemaoption passed as the second argument to PrismaNeon is correct per the official Prisma Neon adapter documentation.content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (2)
24-24: Verify minimum version requirement.Please confirm that v6.15.0 is the correct minimum version requirement for the GA features described, as the documentation mentions GA starting from v6.16.0.
There seems to be a potential inconsistency - the intro states GA is "as of v6.16.0" but the prerequisites mention "v6.15.0 (or later)". Please verify which version is the actual minimum requirement for GA usage.
95-205: Inconsistent import paths between examples.The code examples mix different import approaches - some use
'./generated/prisma'while others should be consistent. Since the generator configuration shows a customoutput = "../generated/prisma", all examples should use the generated path or remove the custom output entirely.For consistency across all examples, either:
- Use the custom generated path consistently:
-import { PrismaClient } from './generated/prisma' +import { PrismaClient } from '../generated/prisma'
- Or remove the custom
outputfrom the generator configuration and use@prisma/clientconsistently throughout all examples.Likely an incorrect or invalid review comment.
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
Show resolved
Hide resolved
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
Outdated
Show resolved
Hide resolved
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
Show resolved
Hide resolved
content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (2)
285-289: Typo in tab label: “Neon Serverles”.Correct spelling to “Neon Serverless”.
-<TabItem value="Neon Serverles"> +<TabItem value="Neon Serverless">
317-336: Import path mismatch with custom output (Preview section).Generator sets
output = "../generated/prisma", so imports from@prisma/clientwill fail. Align to the generated path (consistent with other examples).-import { PrismaClient } from '@prisma/client' +import { PrismaClient } from './generated/prisma'Apply to:
- D1 example (Line 317)
- PlanetScale example (Line 354)
- Neon Serverless example (Line 397)
Also applies to: 354-359, 397-406
🧹 Nitpick comments (5)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (5)
38-42: Grammar: “need to re‑generate”.-To make the configuration take effect, you need re-generate Prisma Client: +To make the configuration take effect, you need to re-generate Prisma Client:
49-89: Adapter list looks correct. Consider a CockroachDB note.Package names look right; CockroachDB uses the Postgres adapter. Consider adding a short note “CockroachDB uses @prisma/adapter-pg; no dedicated Cockroach adapter.” (optional). (prisma.io)
215-216: Minor style: version notation.Use consistent “v6.14.0” (no extra dot).
-The Rust-free version of Prisma ORM has been in Preview from versions v6.7.0 to v.6.14.0. +The Rust-free version of Prisma ORM has been in Preview from versions v6.7.0 to v6.14.0.
239-243: Grammar: “need to re‑generate”.-To make the feature flags take effect, you need re-generate Prisma Client: +To make the feature flags take effect, you need to re-generate Prisma Client:
280-284: CockroachDB via Postgres adapter — verify and optionally annotate.CockroachDB install/usage via
@prisma/adapter-pgmatches current guidance; consider adding a one‑liner note explaining there’s no dedicated Cockroach adapter. (prisma.io)Also applies to: 386-394
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx(2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
📚 Learning: 2025-08-11T09:40:55.237Z
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
Applied to files:
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
🪛 LanguageTool
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
[grammar] ~15-~15: There might be a mistake here.
Context: ... "client"field needs to be set on the on thegeneratorblock - nobinaryTargets` ...
(QB_NEW_EN)
[grammar] ~101-~101: There might be a mistake here.
Context: ...ctionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
[grammar] ~119-~119: There might be a mistake here.
Context: ...isma/adapter-d1' export interface Env { DB: D1Database } export default { asy...
(QB_NEW_EN)
[grammar] ~156-~156: There might be a mistake here.
Context: ....env.DATABASE_URL, fetch: undiciFetch }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
[grammar] ~190-~190: There might be a mistake here.
Context: ...ctionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: runner / linkspector
- GitHub Check: Check internal links
- GitHub Check: Lost Pixel
🔇 Additional comments (3)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (3)
7-7: GA claim needs verification (docs still show Preview path).Official docs currently describe the Rust‑free path as available since v6.7.0 via the
queryCompiler+driverAdaptersPreview features and do not mentionengineType = "client". Please confirm v6.16.0 has promoted this to GA and thatengineType = "client"is the correct setting. If not GA, revert the wording and steps to the Preview flow. (prisma.io)If it’s still Preview, apply:
-As of [v6.16.0](https://pris.ly/release/6.16.0), usage of Prisma ORM without [Rust engine](/orm/more/under-the-hood/engines) binaries on PostgreSQL, CockroachDB, Neon, MySQL, PlanetScale, SQLite, D1 & MS SQL Server databases has been [Generally Available](/orm/more/releases#generally-available-ga). +As of v6.7.0, you can use Prisma ORM without [Rust engine](/orm/more/under-the-hood/engines) binaries on PostgreSQL, CockroachDB, Neon, MySQL, PlanetScale, SQLite, D1 & MS SQL Server databases (Preview via `queryCompiler` + `driverAdapters`). See the release notes for current maturity.
24-25: Version prerequisite andengineType = "client"need confirmation.
- If GA is tied to a specific version, “v6.15.0 (or later)” may be inaccurate; likely “v6.16.0 (or later)” or still “v6.7.0+ (Preview)”.
- Public docs list only
binary/libraryengine types today; please confirmengineType = "client"is valid and documented for v6.16.0. If not, revert to the Preview flags (queryCompiler,driverAdapters). (prisma.io)-- Prisma ORM v6.15.0 (or later) +- Prisma ORM v6.16.0 (or later)If still Preview, replace the generator block with:
-generator client { - provider = "prisma-client-js" // or `prisma-client` - output = "../generated/prisma" - engineType = "client" // enable Prisma ORM without Rust -} +generator client { + provider = "prisma-client-js" // or `prisma-client` + previewFeatures = ["queryCompiler", "driverAdapters"] + output = "../generated/prisma" +}Also applies to: 28-34
95-104: Examples LGTM; imports align with custom output path.Also applies to: 105-113, 114-136, 137-149, 150-159, 160-184, 185-193, 194-207
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
Outdated
Show resolved
Hide resolved
…300-no-rust-engine.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 5
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
content/200-orm/050-overview/500-databases/200-database-drivers.mdx (1)
121-131: Fix incorrect import path in the “6.6.0 and later” example.Unless you’re demonstrating a custom output path, the standard import is from '@prisma/client'. If you intend to show custom output, match the path to the earlier output example.
Apply one of:
Option A (standard import):
-import { PrismaClient } from '../prisma/prisma-client' +import { PrismaClient } from '@prisma/client'Option B (custom output matching earlier example):
-import { PrismaClient } from '../prisma/prisma-client' +import { PrismaClient } from '../src/generated/prisma'content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx (1)
115-120: Invalid CLI flag:prisma initdoes not support--output.The
outputpath is configured in the generator block, not viaprisma init. Please remove the flag to avoid copy/paste errors. (prisma.io)-npx prisma init --output ../app/generated/prisma +npx prisma init +// Then set `output` in the generator block if desired.
♻️ Duplicate comments (4)
content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx (1)
29-31: Fix "driver vs adapter" wording for accuracy.The phrase "native JS database driver" is inconsistent with the package example (
@prisma/adapter-pg) which is an adapter. The wording should clarify the distinction between the underlying driver and the Prisma adapter.- The database connection pool is maintained by the native JS database driver you install (e.g., `@prisma/adapter-pg` for PostgreSQL). + The database connection pool is maintained by the underlying JS database driver (for example, `pg`, Neon serverless, or PlanetScale serverless) that you use via a Prisma driver adapter (for example, `@prisma/adapter-pg`, `@prisma/adapter-neon`, or `@prisma/adapter-planetscale`).content/200-orm/050-overview/500-databases/200-database-drivers.mdx (1)
15-15: Fix version text/URL mismatch for the release link.Anchor says v6.15.0 but URL points to 6.16.0. Align them.
Apply one of the diffs:
-As of [v6.15.0](https://pris.ly/release/6.16.0), Prisma ORM can be used without Rust engines in production applications. Learn more [here](/orm/prisma-client/setup-and-configuration/no-rust-engine). +As of [v6.15.0](https://pris.ly/release/6.15.0), Prisma ORM can be used without Rust engines in production applications. Learn more [here](/orm/prisma-client/setup-and-configuration/no-rust-engine).or
-As of [v6.15.0](https://pris.ly/release/6.16.0), Prisma ORM can be used without Rust engines in production applications. Learn more [here](/orm/prisma-client/setup-and-configuration/no-rust-engine). +As of [v6.16.0](https://pris.ly/release/6.16.0), Prisma ORM can be used without Rust engines in production applications. Learn more [here](/orm/prisma-client/setup-and-configuration/no-rust-engine).If GA actually landed in 6.15.0, keep the first diff; otherwise use the second. Please confirm the exact GA version. (github.com)
content/200-orm/050-overview/500-databases/890-neon.mdx (1)
119-121: Neon serverless driver is still Preview — GA claim and link are incorrect.The current docs state this feature is Preview (available since v5.4.2) and the page title includes “(Preview)”. Please revert the GA claim and point to the Preview guidance. Also consider restoring “(Preview)” in the section heading to keep anchors stable. (prisma.io)
-This feature has been Generally Available since Prisma ORM [v6.16.0](https://pris.ly/release/6.16.0). +This feature is available in Preview from Prisma ORM v5.4.2 and later. See the current setup guide. +// Link to the Neon (Preview) section: +// https://www.prisma.io/docs/guides/database/neon#how-to-use-neons-serverless-driver-with-prisma-orm-previewcontent/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx (1)
31-33: Reword “driver vs adapter” (use driver packages as examples, not adapters).This still reads as if adapters are drivers. Suggested wording matches prior feedback. (prisma.io)
-- The database connection pool is maintained by the native JS database driver you install (e.g., `@prisma/adapter-pg` for PostgreSQL). +- The database connection pool is maintained by the underlying JS database driver (for example, `pg`, Neon serverless, or PlanetScale serverless) that you use via a Prisma driver adapter (for example, `@prisma/adapter-pg`, `@prisma/adapter-neon`, or `@prisma/adapter-planetscale`).
🧹 Nitpick comments (6)
content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx (1)
36-36: Remove extra space before closing tip block.There's an unnecessary space before the closing
:::which creates a formatting issue.- ::: + :::content/200-orm/050-overview/500-databases/200-database-drivers.mdx (1)
85-86: Keep PlanetScale anchor consistent with section above.Same as Lines 68–71: ensure the anchor reflects the latest title (Preview vs not). Consider deduplicating the link target via a shared reference to avoid divergence in future edits.
content/200-orm/050-overview/500-databases/890-neon.mdx (2)
123-127: Typo: “istall” → “install”.Minor spelling fix. Detected by linter.
-To get started, istall the Prisma ORM adapter for Neon: +To get started, install the Prisma ORM adapter for Neon:
129-144: If still Preview, re-introduce minimal setup steps.The Preview flow requires enabling driverAdapters (and often queryCompiler) and running prisma generate. Consider adding a short prerequisite note or link to avoid broken setups. (prisma.io)
Update your Prisma Client instance: +// If you haven't enabled the Preview features yet, add to schema.prisma: +// generator client { +// provider = "prisma-client-js" +// previewFeatures = ["driverAdapters"] // and "queryCompiler" if using the Rust-free preview +// } +// Then run: npx prisma generatecontent/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx (2)
36-37: Blog link ok; consider softening “moved away” phrasing.Given the ongoing Preview status, “moved away” may overstate. Consider “transitioning away from Rust engines” to align with current messaging. (prisma.io)
-Curious why we moved away from the Rust engine? +Curious why we’re transitioning away from Rust engines?
16-26: Would you like a single-source snippet that stays correct across GA/Preview?I can generate conditional snippets (shortcodes) that resolve to either the Preview or GA instructions based on a front-matter flag, preventing future drift.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (6)
content/200-orm/050-overview/500-databases/200-database-drivers.mdx(3 hunks)content/200-orm/050-overview/500-databases/890-neon.mdx(2 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx(2 hunks)content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx(7 hunks)content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx(7 hunks)content/200-orm/500-reference/050-prisma-client-reference.mdx(2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- content/200-orm/500-reference/050-prisma-client-reference.mdx
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
📚 Learning: 2025-08-11T09:40:55.237Z
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
Applied to files:
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx
🪛 LanguageTool
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
[grammar] ~17-~17: There might be a mistake here.
Context: ...ineTypefields on thegenerator` block - no query engine binary that's downloaded...
(QB_NEW_EN)
[grammar] ~18-~18: There might be a mistake here.
Context: ...ectory with your generated Prisma Client - required usage of driver adapters for da...
(QB_NEW_EN)
[grammar] ~19-~19: There might be a mistake here.
Context: ...pters for database connection management - no query engine binary that's downloaded...
(QB_NEW_EN)
[grammar] ~20-~20: There might be a mistake here.
Context: ...ectory with your generated Prisma Client - required usage of [driver adapters](/orm...
(QB_NEW_EN)
[grammar] ~104-~104: There might be a mistake here.
Context: ...ctionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
[grammar] ~122-~122: There might be a mistake here.
Context: ...isma/adapter-d1' export interface Env { DB: D1Database } export default { asy...
(QB_NEW_EN)
[grammar] ~159-~159: There might be a mistake here.
Context: ....env.DATABASE_URL, fetch: undiciFetch }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
[grammar] ~193-~193: There might be a mistake here.
Context: ...ctionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapte...
(QB_NEW_EN)
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx
[grammar] ~38-~38: There might be a mistake here.
Context: ...ust-latest-performance-benchmarks). ::: ## General considerations when deploying to...
(QB_NEW_EN)
content/200-orm/050-overview/500-databases/890-neon.mdx
[grammar] ~123-~123: Ensure spelling is correct
Context: .../release/6.16.0). ::: To get started, istall the Prisma ORM adapter for Neon: ```te...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
content/200-orm/050-overview/500-databases/200-database-drivers.mdx
[grammar] ~69-~69: There might be a mistake here.
Context: ...r-with-prisma-orm) (and Vercel Postgres) - [PlanetScale](/orm/overview/databases/pla...
(QB_NEW_EN)
[grammar] ~81-~81: There might be a mistake here.
Context: ...rs with the specific database providers: - [PostgreSQL](/orm/overview/databases/post...
(QB_NEW_EN)
[grammar] ~82-~82: There might be a mistake here.
Context: ...ecific database providers: - PostgreSQL - [MySQL/MariaDB](/orm/overview/databases/m...
(QB_NEW_EN)
[grammar] ~83-~83: There might be a mistake here.
Context: ...e-node-postgres-driver) - MySQL/MariaDB - [MS SQL Server](/orm/overview/databases/s...
(QB_NEW_EN)
[grammar] ~84-~84: There might be a mistake here.
Context: ...ing-the-mariadb-driver) - MS SQL Server - [Neon](/orm/overview/databases/neon#how-t...
(QB_NEW_EN)
[grammar] ~85-~85: There might be a mistake here.
Context: ...ver#using-the-node-mssql-driver) - Neon - [PlanetScale](/orm/overview/databases/pla...
(QB_NEW_EN)
[grammar] ~86-~86: There might be a mistake here.
Context: ...s-driver-with-prisma-orm) - PlanetScale - [Turso](/orm/overview/databases/turso#how...
(QB_NEW_EN)
[grammar] ~87-~87: There might be a mistake here.
Context: ...driver-with-prisma-orm-preview) - Turso - [Cloudflare D1](/orm/overview/databases/c...
(QB_NEW_EN)
content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx
[grammar] ~36-~36: There might be a mistake here.
Context: ...ust-latest-performance-benchmarks). ::: ## General considerations when deploying to...
(QB_NEW_EN)
[grammar] ~374-~374: There might be a mistake here.
Context: ...verless-driver-with-prisma-orm-preview)) - manually remove the conflicting cache ...
(QB_NEW_EN)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: runner / linkspector
- GitHub Check: Lost Pixel
🔇 Additional comments (17)
content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx (3)
14-35: LGTM! Well-structured documentation update for Prisma ORM's Rust-free mode.The updated tip section clearly explains the new GA configuration for running Prisma ORM without Rust binaries. The content accurately reflects the transition from preview features to the stable
engineType = "client"approach, with proper version references and helpful links to additional resources.
248-248: LGTM! Consistent database connection configuration guidance.The repeated pattern of ensuring proper database connection configuration across different database providers (PostgreSQL, PlanetScale, Neon) is consistent and helpful for users following the deployment guides.
Also applies to: 403-403, 533-533
237-237: Script to verify PostgreSQL adapter link added; awaiting results.content/200-orm/050-overview/500-databases/200-database-drivers.mdx (2)
68-71: PlanetScale link still targets a “Preview” anchor; confirm final slug.Neon’s link omits “-preview” while PlanetScale uses “-preview”. Verify the current headings/anchors for 6.16 docs and update if PlanetScale is no longer marked Preview.
Suggested (only if the anchor changed):
-- [PlanetScale](/orm/overview/databases/planetscale#how-to-use-the-planetscale-serverless-driver-with-prisma-orm-preview) +- [PlanetScale](/orm/overview/databases/planetscale#how-to-use-the-planetscale-serverless-driver-with-prisma-orm)Reference for current anchor shows “(Preview)”. (prisma.io)
151-152: “Preview feature” wording may be outdated; verify status and adjust.If driver adapters are still Preview in 6.16.0, keep this wording; if not, drop “Preview” here for consistency with the rest of the page.
Example edit (only if GA):
-Since Prisma 5.9.0, when using the driver adapters Preview feature along with a [custom output path for Prisma Client]... +Since Prisma 5.9.0, when using driver adapters along with a [custom output path for Prisma Client]...Note: Current public docs still label several adapter pages as “Preview”. (prisma.io)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (7)
7-7: Verify GA claim for “no Rust engine” in v6.16.0.Live docs still describe this as available since v6.7.0 with Preview feature flags, not GA. Please confirm the release notes for 6.16.0 before publishing this GA statement. If GA isn’t landing in 6.16.0, revert to the current wording (“As of v6.7.0…”) and keep the Preview flow. Sources: “No Rust engine” docs and changelog/blog. (prisma.io)
-As of [v6.16.0](https://pris.ly/release/6.16.0), usage of Prisma ORM without ... +As of v6.7.0, you can use Prisma ORM without ...
27-27: Align minimum version with reality (6.15.0 vs 6.7.0 vs 6.16.0).If GA truly lands in 6.16.0 and requires
engineType = "client", set this to “v6.16.0 (or later)”. If not, keep “v6.7.0 (or later)” to match the current Preview docs. (prisma.io)-- Prisma ORM v6.15.0 (or later) +// If GA: Prisma ORM v6.16.0 (or later) +// If Preview: Prisma ORM v6.7.0 (or later)
39-46: LGTM — regenerate step.Command and phrasing look good.
51-92: Adapter package names look correct.PostgreSQL, SQLite, D1, MySQL/MariaDB, PlanetScale, MSSQL, CockroachDB (via pg), and Neon match current docs. (prisma.io)
98-210: Examples compile and align with custom output path.All imports use
./generated/prisma, consistent withoutput = "../generated/prisma". Neon, PlanetScale, and D1 snippets match adapter usage in live docs. (prisma.io)
216-219: Good separation for “older versions (Preview)”.Clear guidance to keep Preview instructions isolated from the GA/modern flow.
415-418: LGTM — closing details block.Structure and wording are fine.
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx (5)
136-137: Good: explicit call-out for Vercel Postgres → Neon adapter.Nice clarity that Vercel Postgres requires
@prisma/adapter-neon. ✅
269-270: PlanetScale link anchor still says “preview” — confirm status.PlanetScale serverless driver docs remain marked Preview today; the anchor is correct. Keep as-is unless GA is announced. (prisma.io)
391-392: Neon cross-link matches Neon page (but ensure Preview vs GA is consistent).If you revert Neon to Preview in its page, this cross-link remains valid. (prisma.io)
45-56: Edge compatibility note is accurate.pg isn’t supported in Vercel Edge; using an edge-compatible driver with an adapter is the right guidance.
508-527: Fluid example looks good.Using
pgvia@prisma/adapter-pgwithattachDatabasePoolfits Fluid’s Node.js runtime.
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
Outdated
Show resolved
Hide resolved
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (2)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (2)
17-21: Do not instruct to set engineType="client"; keep Preview bullets.Official docs list valid engineType values as only "binary" or "library"; the Rust‑free flow uses preview flags and explicitly says “no engineType field”. Adjust bullets accordingly.
-- no `binaryTargets` field on the `generator` block -... -- `engineType` needs to be set to `"client"` on the `generator` block +- no `binaryTargets` and `engineType` fields on the `generator` blockSources: Engines doc (engineType valid values), no‑Rust‑engine page. (prisma.io)
7-7: Remove GA wording; feature is still in Preview
Current docs state Rust-free Prisma ORM is available since v6.7.0 under thequeryCompiler+driverAdapterspreview flags—no GA note exists (prisma.io)-As of [v6.16.0](https://pris.ly/release/6.16.0), usage of Prisma ORM without [Rust engine](/orm/more/under-the-hood/engines) binaries on PostgreSQL, CockroachDB, Neon, MySQL, PlanetScale, SQLite, D1 & MS SQL Server databases has been [Generally Available](/orm/more/releases#generally-available-ga). +As of v6.7.0, you can use Prisma ORM without [Rust engine](/orm/more/under-the-hood/engines) binaries on PostgreSQL, CockroachDB, Neon, MySQL, PlanetScale, SQLite, D1 & MS SQL Server databases.
🧹 Nitpick comments (4)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (4)
15-16: Remove duplicated heading line.Line 15 repeats the heading from Line 13.
-The main technical differences if you're using Prisma ORM without a Rust engine are:
22-24: Warning block contradicts examples; align generator guidance.Rust‑free flow is validated in docs with prisma‑client‑js; the new prisma‑client generator is still maturing. Reword to avoid recommending the opposite.
-:::warning -The Rust-free version of Prisma ORM has been thoroughly tested with the `prisma-client` generator (see below), not with `prisma-client-js`. Use the old generator at your discretion. -::: +:::warning +This Rust‑free flow is validated with the `prisma-client-js` generator. The new `prisma-client` generator is still maturing; use it at your discretion. +:::Refs: Generator docs (js generator default), v6.15 blog noting prisma‑client progress. (prismagraphql.com, prisma.io)
42-48: Grammar and heading casing.Use “Regenerate” and add “to”.
-### 2. Re-generate Prisma Client +### 2. Regenerate Prisma Client @@ -To make the configuration take effect, you need re-generate Prisma Client: +To make the configuration take effect, you need to regenerate Prisma Client:
101-110: Make imports match configured output path.Your generator sets
output = "../generated/prisma", but examples import from./generated/prisma. Align paths for consistency.-import { PrismaClient } from './generated/prisma' +import { PrismaClient } from '../generated/prisma'Apply to lines 105, 114, 122, 146, 159, 169, 194, 202.
Also applies to: 111-119, 120-142, 143-155, 156-165, 166-190, 191-199, 200-214
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx(2 hunks)content/250-postgres/1100-integrations/500-vscode.mdx(1 hunks)content/250-postgres/300-database/650-direct-connections.mdx(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- content/250-postgres/300-database/650-direct-connections.mdx
🚧 Files skipped from review as they are similar to previous changes (1)
- content/250-postgres/1100-integrations/500-vscode.mdx
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
📚 Learning: 2025-08-11T09:40:55.237Z
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
Applied to files:
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: Cloudflare Pages
- GitHub Check: runner / linkspector
- GitHub Check: Lost Pixel
🔇 Additional comments (4)
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx (4)
30-31: Prerequisites version should be v6.7.0+ per current docs.Unless GA is confirmed, revert to the documented minimum.
-- Prisma ORM v6.15.0 (or later) +- Prisma ORM v6.7.0 (or later)Source: No‑Rust‑engine page. (prisma.io)
50-95: CockroachDB adapter compatibility needs confirmation.You list
@prisma/adapter-pgfor CockroachDB. There are issues reporting incompatibility withprovider = "cockroachdb"when using driver adapters. Please verify current 6.16.x status or add a note.References: Issue threads and current docs. (github.com, prisma.io)
215-218: LGTM.Step 5 text is clear and matches the documented flow.
418-421: LGTM.Preview section closing and summary read well.
content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (4)
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx (4)
170-181: Enable driverAdapters (and optionally queryCompiler) in schema for Vercel PostgresExamples that use Neon’s serverless driver need the driverAdapters feature; consider also showing queryCompiler for Rust‑free builds. (prisma.io)
generator client { - provider = "prisma-client-js" + provider = "prisma-client-js" + previewFeatures = ["driverAdapters"] // add ["queryCompiler"] for Rust-free Preview } datasource db {
295-306: PlanetScale section: add driverAdapters to the generatorUsing the PlanetScale serverless driver with Prisma requires the driverAdapters Preview feature. (prisma.io)
generator client { - provider = "prisma-client-js" + provider = "prisma-client-js" + previewFeatures = ["driverAdapters"] } datasource db {
417-428: Neon section: add driverAdapters to the generator (and optionally queryCompiler)Neon serverless + Prisma needs driverAdapters; optionally show queryCompiler for Rust‑free Preview. (prisma.io)
generator client { - provider = "prisma-client-js" + provider = "prisma-client-js" + previewFeatures = ["driverAdapters"] // add ["queryCompiler"] for Rust-free Preview } datasource db {
135-136: CLI flag issue:prisma initdoesn’t take--output; setoutputin the generator insteadUse
npx prisma init(no flag), then configureoutputin the generator block. (prisma.io)-npx prisma init --output ../app/generated/prisma +npx prisma init +# then set `output = "app/generated/prisma"` in your `generator client { ... }`
♻️ Duplicate comments (2)
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx (2)
36-41: engineType "client" is invalid; Rust‑free mode still Preview—fix generator and GA claim
- Valid engineType values are only "binary" or "library"; there is no "client". Rust‑free mode is still documented behind previewFeatures (queryCompiler + driverAdapters). Also mark "prisma-client" as Preview. (prisma.io)
Apply:
generator client { - provider = "prisma-client-js" // or "prisma-client" - engineType = "client" + provider = "prisma-client-js" // or "prisma-client" (Preview) + // Rust-free Preview (v6.7.0+): + previewFeatures = ["queryCompiler", "driverAdapters"] + // optional: + // output = "app/generated/prisma" } -Prisma ORM without Rust binaries has been [Generally Available](/orm/more/releases#generally-available-ga) since [v6.16.0](https://pris.ly/release/6.16.0). +Prisma ORM without Rust binaries is currently in Preview. Follow the setup guide linked below.
47-51: Clarify “driver vs adapter” and pooling wordingAdapters aren’t drivers. The pool is owned by the JS driver that you use via a Prisma driver adapter. (prisma.io)
- No Rust query engine binary is downloaded or shipped. -- The database connection pool is maintained by the native JS database driver you install (e.g., `@prisma/adapter-pg` for PostgreSQL). +- The connection pool is maintained by the underlying JS database driver (for example, `pg`, Neon serverless, PlanetScale serverless) that you use via a Prisma driver adapter (for example, `@prisma/adapter-pg`, `@prisma/adapter-neon`, `@prisma/adapter-planetscale`).
🧹 Nitpick comments (1)
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx (1)
119-121: Be precise: this 1 MB limit applies to Edge (Hobby) code size after gzipConsider clarifying it’s the Edge Runtime Hobby plan code size limit (gzip), not a general Vercel account limit. (vercel.com)
-Vercel has a size limit of 1 MB on free accounts +On the Edge Runtime, the Hobby plan enforces a 1 MB code size limit (after gzip)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx(7 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
📚 Learning: 2025-08-11T09:40:55.237Z
Learnt from: ankur-arch
PR: prisma/docs#7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
Applied to files:
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: Check internal links
- GitHub Check: runner / linkspector
- GitHub Check: Lost Pixel
- GitHub Check: Cloudflare Pages
🔇 Additional comments (1)
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx (1)
152-153: LGTM: Vercel Postgres ↔ Neon note and adapter choice are correctVercel Postgres is powered by Neon; recommending
@prisma/adapter-neonhere is accurate. (examples.vercel.com)
Summary by CodeRabbit