wmadden-electric · Oct 9, 2026 · Oct 9, 2026 · coderabbitai · Oct 9, 2026
diff --git a/apps/docs/content/docs/(index)/full-stack-tutorial.mdx b/apps/docs/content/docs/(index)/full-stack-tutorial.mdx
@@ -14,8 +14,8 @@ It uses the `hono` template so you get a small API you can verify with curl at e
 
 ## Prerequisites
 
-- Node.js 22.18 or newer (on the 24 line, 24.11 or newer; 24 recommended), or Bun
-- npm 11.6.0 or newer, if you use npm. Node.js 22 comes with npm 10, so run `npm install --global npm@11` first; the [create-prisma prerequisites](/prisma-orm/create-prisma#prerequisites) explain why
+- Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer (24 recommended), or Bun
+- If you use npm, the npm that ships with your Node.js release (npm 10 on Node.js 22)
 - A [Prisma Data Platform account](https://pris.ly/pdp) for the deploy step, free to create, with no credit card needed on the [Free plan](#what-the-free-plan-includes)
 - No database needed: local runs provision a local Prisma Postgres, and deploys provision a real one, both from your Composer declaration
 
@@ -75,7 +75,7 @@ The prompt uses npm and Node.js. On Bun, replace `npm create prisma@latest --` w
 ```text
 Create a new Hono API composed with Prisma Composer and Prisma ORM, run it locally, and deploy it to Prisma Compute.
 
-Check the versions first: `node --version` must print 22.18 or newer (on the 24 line, 24.11 or newer). If you use npm, `npm --version` must print 11.6.0 or newer; Node.js 22 comes with npm 10, so if npm is older, run `npm install --global npm@11` before step 1.
+Check the Node.js version first: `node --version` must print 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer. The npm that ships with your Node.js release works; on Node.js 22 that is npm 10.
 
 1. Scaffold: `npm create prisma@latest -- my-app --template hono --provider postgres --yes`. Then run `npx prisma@latest init` in `my-app` to confirm the Prisma agent skills the scaffold installed are current, and use them.
 2. Read `module.ts` and `service.ts` first: the Composer module provisions the database and the service, and it is what `dev` and `deploy` operate on.

diff --git a/apps/docs/content/docs/(index)/getting-started.mdx b/apps/docs/content/docs/(index)/getting-started.mdx
@@ -12,8 +12,8 @@ Coming from an earlier version? [Coming from Prisma ORM 7](/orm/coming-from-pris
 
 ## Prerequisites
 
-- **Node.js 22.18 or newer; on the 24 line, 24.11 or newer.** Check with `node --version`. Node.js 24 is recommended.
-- **npm 11.6.0 or newer, if you start a new project with npm.** Check with `npm --version`. Node.js 22 comes with npm 10, and `npm create prisma@latest` stops on npm 10 before it writes any files, so update npm first with `npm install --global npm@11`. pnpm, Bun, and Yarn 2 or newer are also supported. The [create-prisma prerequisites](/prisma-orm/create-prisma#prerequisites) have the details.
+- **Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer.** Check with `node --version`. Node.js 24 is recommended.
+- **A package manager.** The npm that ships with your Node.js release works; on Node.js 22 that is npm 10. pnpm, Bun, and Yarn 4.10 or newer are also supported.
 
 ## Start a new project
 
@@ -70,7 +70,7 @@ Create a new [framework] application with Prisma ORM, seed it, and run it locall
 
 If I have not told you which framework, stop and ask before scaffolding. Valid --template values: minimal (the default), next, hono, nuxt, astro, nest, svelte, tanstack-start, elysia.
 
-Check the versions first: `node --version` must print 22.18 or newer (on the 24 line, 24.11 or newer). If you use npm, `npm --version` must print 11.6.0 or newer; Node.js 22 comes with npm 10, so if npm is older, run `npm install --global npm@11` before step 1.
+Check the Node.js version first: `node --version` must print 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer. The npm that ships with your Node.js release works; on Node.js 22 that is npm 10.
 
 1. Scaffold the app: `npm create prisma@latest -- my-app --template [framework] --provider postgres --yes`.
 2. Get a database connection string: use the one I give you, or create a Prisma Postgres database with `npx create-db@latest` and show me the claim URL it prints. Export it as `DATABASE_URL` in the shell; the generated scripts read the environment variable, not `.env`.

diff --git a/apps/docs/content/docs/(index)/index.mdx b/apps/docs/content/docs/(index)/index.mdx
@@ -119,7 +119,7 @@ Create a new [framework] application with Prisma ORM against my existing Postgre
 
 If I have not given you a connection string, stop and ask; do not invent one. Valid --template values: minimal (the default), next, hono, nuxt, astro, nest, svelte, tanstack-start, elysia.
 
-Check the versions first: `node --version` must print 22.18 or newer (on the 24 line, 24.11 or newer). If you use npm, `npm --version` must print 11.6.0 or newer; Node.js 22 comes with npm 10, so if npm is older, run `npm install --global npm@11` before step 1.
+Check the Node.js version first: `node --version` must print 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer. The npm that ships with your Node.js release works; on Node.js 22 that is npm 10.
 
 1. Scaffold: `npm create prisma@latest -- my-app --template [framework] --provider postgres --yes`.
 2. Export my connection string as `DATABASE_URL` in the shell; the generated scripts read the environment variable, not `.env`. From the project directory: `npm run db:init`, then start `npm run dev` in the background and verify the sample query returns data. Sample users are seeded automatically on the app's first query; there is no separate seed script.

diff --git a/apps/docs/content/docs/(index)/prisma-compute/deploy.mdx b/apps/docs/content/docs/(index)/prisma-compute/deploy.mdx
@@ -19,7 +19,7 @@ Both paths meet in the same [deploy step](#2-deploy), because Composer treats ev
 
 Before you start, make sure you have:
 
-- **Node.js 22.18 or newer.** Composer hands your TypeScript entry file straight to Node, and running `.ts` files directly needs 22.18.0 or later. On older versions, Composer commands stop at `ERR_UNKNOWN_FILE_EXTENSION`.
+- **Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer.** Composer hands your TypeScript entry file straight to Node, and running `.ts` files directly needs 22.18.0 or later. On older versions, Composer commands stop at `ERR_UNKNOWN_FILE_EXTENSION`.
 - **[Bun](https://bun.sh).** Prisma Compute runs deployed apps on Bun, so your server code targets it, and `bun build` produces the self-contained entry file a deploy needs.
 - **A [Prisma Data Platform account](https://pris.ly/pdp)**, free to create. You only need it for the deploy step; [local development](/local-development) runs without an account.
 
@@ -248,7 +248,7 @@ Build [what you want] as a Prisma Composer app and deploy it to Prisma Compute u
 Notes:
 - After installing @prisma/composer, install its agent skill so you use the real API: `npx prisma skills sync` (the skill ships inside the package; run `npx prisma skills list` to confirm).
 - Before deploying, run `npx prisma auth whoami`; if I am not signed in, stop and ask me to run `npx prisma auth login` (it opens a browser).
-- Composer needs Node.js 22.18 or newer, and server code targets Bun. Read the port with `service.port()` and bind 0.0.0.0. For a Next.js service, use the nextjs build adapter and set `output: "standalone"`.
+- Composer needs Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer, and server code targets Bun. Read the port with `service.port()` and bind 0.0.0.0. For a Next.js service, use the nextjs build adapter and set `output: "standalone"`.
 - Composer does not build; produce one self-contained entry file per service (for example `bun build --target=bun`), then run it locally with `npx prisma dev module.ts` and verify each service's local URL responds.
 - Deploy with `npx prisma deploy module.ts` and verify the printed public URL with curl.
 - To give a service a database, declare `deps: { db: rawPostgres() }` (imported from @prisma/composer-prisma-cloud) and build the client from the injected `db.url`; do not read connection strings from process.env. For a database typed by Prisma ORM, use `postgres(contract)` from @prisma/composer-prisma-cloud/orm instead.

diff --git a/apps/docs/content/docs/(index)/prisma-orm/add-to-existing-project/mongodb.mdx b/apps/docs/content/docs/(index)/prisma-orm/add-to-existing-project/mongodb.mdx
@@ -10,7 +10,7 @@ This page uses MongoDB. [Use PostgreSQL instead](/prisma-orm/add-to-existing-pro
 
 On this page you add Prisma ORM to an app whose MongoDB database already has collections. You run `orm init`, write a contract that describes your collections, and run two queries. The contract is the file that holds your models. In earlier Prisma ORM versions, it was `schema.prisma`.
 
-Your app must reach its MongoDB database and run on Node.js 22.18 or newer. A single `mongod` server is enough. You need a replica set only for transactions and change streams, and MongoDB Atlas already runs one.
+Your app must reach its MongoDB database and run on Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer. A single `mongod` server is enough. You need a replica set only for transactions and change streams, and MongoDB Atlas already runs one.
 
 If your database has no collections yet, follow [Add Prisma ORM and MongoDB to an existing app](/prisma-orm/quickstart/existing-app/mongodb) instead, which creates the collections for you. If you want Prisma ORM to create a new app for you, follow [Create a new app with MongoDB](/prisma-orm/quickstart/mongodb).
 

diff --git a/apps/docs/content/docs/(index)/prisma-orm/add-to-existing-project/postgresql.mdx b/apps/docs/content/docs/(index)/prisma-orm/add-to-existing-project/postgresql.mdx
@@ -10,7 +10,7 @@ This page uses PostgreSQL. [Use MongoDB instead](/prisma-orm/add-to-existing-pro
 
 On this page you add Prisma ORM to an app whose PostgreSQL database already has tables. You run `orm init`, generate the contract from your tables, run two queries, and apply your first change to the tables. The contract is the file that holds your models. In Prisma ORM 7, it was `schema.prisma`.
 
-Your app must reach its PostgreSQL database and run on Node.js 22.18 or newer. Work against a development copy of your database, not production. [Step 9](#9-make-your-first-change-to-the-tables) shows how to apply your changes to production afterwards.
+Your app must reach its PostgreSQL database and run on Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer. Work against a development copy of your database, not production. [Step 9](#9-make-your-first-change-to-the-tables) shows how to apply your changes to production afterwards.
 
 If your database has no tables yet, follow [Add Prisma ORM and PostgreSQL to an existing app](/prisma-orm/quickstart/existing-app/postgresql) instead, which creates the tables for you. If you want Prisma ORM to create a new app for you, follow [Create a new app with PostgreSQL](/prisma-orm/quickstart/postgresql). If your app uses Prisma ORM 7 today, follow [Prisma ORM 7 to 8 (PostgreSQL)](/guides/upgrade-prisma-orm/postgresql).
 

diff --git a/apps/docs/content/docs/(index)/prisma-orm/create-prisma.mdx b/apps/docs/content/docs/(index)/prisma-orm/create-prisma.mdx
@@ -18,24 +18,10 @@ Use it when you want to start from a working app. If you already have an app, fo
 
 ## Prerequisites
 
-Check both versions before you run the command, because `create-prisma` stops when either one is too old:
+- **Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer.** Check with `node --version`. Node.js 24 is recommended.
+- **A package manager.** The npm that ships with your Node.js release works; on Node.js 22 that is npm 10. pnpm, Bun, and Yarn 4.10 or newer are also supported.
 
-- **Node.js 22.18 or newer; on the 24 line, 24.11 or newer.** Check with `node --version`. Node.js 24 is recommended.
-- **npm 11.6.0 or newer, if you install with npm.** Check with `npm --version`. Every Node.js 22 release comes with npm 10, so on Node.js 22 you have to update npm yourself. Node.js 24.11 and newer already come with a new enough npm.
-
-To update npm:
-
-```bash
-npm install --global npm@11
-```
-
-Older npm releases can crash while they install the Prisma packages. For that reason `create-prisma` checks the npm version before it writes any files, and on an older npm it stops with this message:
-
-```text
-Create command failed: npm 10.9.9 is unsupported. Required: npm 11.6.0 or newer. Older npm releases can crash while resolving Prisma dependencies. Run npm install --global npm@11, then retry create-prisma.
-```
-
-The npm requirement applies only when npm installs the project. pnpm, Bun, and Yarn 2 or newer are also supported, but Yarn 1 is not.
+On any other Node.js version, `create-prisma` stops before it writes any files and prints the required range. It skips this check when you run it with Bun or Deno.
 
 ## Create a project
 
@@ -91,7 +77,7 @@ npm create prisma@latest -- my-app --template next --provider postgres --yes
 | `nest` | NestJS |
 | `svelte` | SvelteKit |
 | `astro` | Astro |
-| `nuxt` | Nuxt |
+| `nuxt` | Nuxt (needs Node.js 22.22.3 or newer on the 22 line, 24.15 or newer on the 24 line, or 26 or newer) |
 | `tanstack-start` | TanStack Start |
 
 Every template supports PostgreSQL and MongoDB, PSL or TypeScript contract authoring, and npm, pnpm, Yarn, and Bun. Each [framework guide](/guides) walks the generated app from the first query to a deploy.

diff --git a/apps/docs/content/docs/(index)/prisma-orm/from-scratch.mdx b/apps/docs/content/docs/(index)/prisma-orm/from-scratch.mdx
@@ -22,7 +22,7 @@ Two commands have new names in Prisma ORM 8. `contract emit` does what `prisma g
 
 ## Prerequisites
 
-- Node.js 22.18 or newer.
+- Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer (24 recommended).
 - A connection string for an empty PostgreSQL database. Step 4 creates the tables and step 5 clears the `User` table on every run, so do not point this page at a database that holds data you need. Any PostgreSQL URL works. If you don't have one, `npx create-db@latest` creates a temporary Prisma Postgres database and prints its connection string, plus a claim URL if you want to keep it.
 
 ## 1. Create the project

diff --git a/apps/docs/content/docs/(index)/prisma-orm/index.mdx b/apps/docs/content/docs/(index)/prisma-orm/index.mdx
@@ -106,7 +106,7 @@ Create a new [framework] application with Prisma ORM, seed it, and run it locall
 
 If I have not told you which framework, stop and ask before scaffolding. Valid --template values: minimal (the default), next, hono, nuxt, astro, nest, svelte, tanstack-start, elysia.
 
-Check the versions first: `node --version` must print 22.18 or newer (on the 24 line, 24.11 or newer). If you use npm, `npm --version` must print 11.6.0 or newer; Node.js 22 comes with npm 10, so if npm is older, run `npm install --global npm@11` before step 1.
+Check the Node.js version first: `node --version` must print 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer. The npm that ships with your Node.js release works; on Node.js 22 that is npm 10.
 
 1. Scaffold the app: `npm create prisma@latest -- my-app --template [framework] --provider postgres --yes`. Then run `npx prisma@latest init` in the project directory so the Prisma agent skills are installed and stay current, and use them.
 2. Get a database connection string: use the one I give you, or create a Prisma Postgres database in the project the app will deploy to: check `npx prisma auth whoami` (if I am not signed in, stop and ask me to run `npx prisma auth login`), then `npx prisma project create my-app` and `npx prisma postgres create mydb`, which prints the connection string once. Export it as `DATABASE_URL` in the shell; the generated scripts read the environment variable.

diff --git a/apps/docs/content/docs/(index)/prisma-orm/quickstart/existing-app/mongodb.mdx b/apps/docs/content/docs/(index)/prisma-orm/quickstart/existing-app/mongodb.mdx
@@ -20,7 +20,7 @@ For what release candidate means, when the final release is expected, and how to
 
 ## Prerequisites
 
-- A project directory with a `package.json`, on Node.js 22.18 or newer.
+- A project directory with a `package.json`, on Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer (24 recommended).
 - A way to run a TypeScript file. This page uses `tsx`. If your project does not have it, run `npm install --save-dev tsx typescript`.
 - An empty MongoDB database, version 8.0 or newer. A single `mongod` server is enough. You need a replica set only for transactions and change streams.
 

diff --git a/apps/docs/content/docs/(index)/prisma-orm/quickstart/existing-app/postgresql.mdx b/apps/docs/content/docs/(index)/prisma-orm/quickstart/existing-app/postgresql.mdx
@@ -20,7 +20,7 @@ For what release candidate means, when the final release is expected, and how to
 
 ## Prerequisites
 
-- A project directory with a `package.json`, on Node.js 22.18 or newer.
+- A project directory with a `package.json`, on Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer (24 recommended).
 - A way to run a TypeScript file. This page uses `tsx`. If your project does not have it, run `npm install --save-dev tsx typescript`.
 - An empty PostgreSQL database, version 15 or newer. Step 2 shows how to get one if you have none.
 

diff --git a/apps/docs/content/docs/(index)/prisma-orm/quickstart/mongodb.mdx b/apps/docs/content/docs/(index)/prisma-orm/quickstart/mongodb.mdx
@@ -20,7 +20,7 @@ For what release candidate means, when the final release is expected, and how to
 
 ## Quick start
 
-You need Node.js 22.18 or newer (on the 24 line, 24.11 or newer); Node.js 24 is recommended. If you use npm, you also need npm 11.6.0 or newer: Node.js 22 comes with npm 10, so run `npm install --global npm@11` first. The [create-prisma prerequisites](/prisma-orm/create-prisma#prerequisites) explain why.
+You need Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer; Node.js 24 is recommended. The npm that ships with your Node.js release works; on Node.js 22 that is npm 10.
 
 ```npm
 npm create prisma@latest -- --provider mongodb --no-deploy

diff --git a/apps/docs/content/docs/(index)/prisma-orm/quickstart/postgresql.mdx b/apps/docs/content/docs/(index)/prisma-orm/quickstart/postgresql.mdx
@@ -20,7 +20,7 @@ For what release candidate means, when the final release is expected, and how to
 
 ## Quick start
 
-You need Node.js 22.18 or newer (on the 24 line, 24.11 or newer); Node.js 24 is recommended. If you use npm, you also need npm 11.6.0 or newer: Node.js 22 comes with npm 10, so run `npm install --global npm@11` first. The [create-prisma prerequisites](/prisma-orm/create-prisma#prerequisites) explain why.
+You need Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer; Node.js 24 is recommended. The npm that ships with your Node.js release works; on Node.js 22 that is npm 10.
 
 ```npm
 npm create prisma@latest -- --provider postgres --no-deploy

diff --git a/apps/docs/content/docs/(index)/prisma-postgres/from-the-cli.mdx b/apps/docs/content/docs/(index)/prisma-postgres/from-the-cli.mdx
@@ -10,7 +10,7 @@ Use the CLI when you want Prisma ORM and Prisma Postgres set up without leaving
 
 ## Start a new app
 
-You need Node.js 22.18 or newer (on the 24 line, 24.11 or newer); Node.js 24 is recommended. If you use npm, you also need npm 11.6.0 or newer: Node.js 22 comes with npm 10, so run `npm install --global npm@11` first. The [create-prisma prerequisites](/prisma-orm/create-prisma#prerequisites) explain why.
+You need Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer; Node.js 24 is recommended. The npm that ships with your Node.js release works; on Node.js 22 that is npm 10.
 
 ```npm
 npm create prisma@latest

diff --git a/...cs/content/docs/(index)/prisma-postgres/import-from-existing-database-mysql.mdx b/...cs/content/docs/(index)/prisma-postgres/import-from-existing-database-mysql.mdx
@@ -15,7 +15,7 @@ You need:
 - the connection URL for the MySQL database you are importing from
 - a Prisma Data Platform account
 - `pgloader`
-- Node.js 24 or newer
+- Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer (24 recommended)
 
 ## 1. Create a Prisma Postgres database
 

diff --git a/apps/docs/content/docs/(index)/prisma-postgres/quickstart/prisma-orm.mdx b/apps/docs/content/docs/(index)/prisma-postgres/quickstart/prisma-orm.mdx
@@ -10,7 +10,7 @@ Create a Prisma ORM app backed by Prisma Postgres.
 
 ## Quick start
 
-You need Node.js 22.18 or newer (on the 24 line, 24.11 or newer); Node.js 24 is recommended. If you use npm, you also need npm 11.6.0 or newer: Node.js 22 comes with npm 10, so run `npm install --global npm@11` first. The [create-prisma prerequisites](/prisma-orm/create-prisma#prerequisites) explain why.
+You need Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer; Node.js 24 is recommended. The npm that ships with your Node.js release works; on Node.js 22 that is npm 10.
 
 ```npm
 npm create prisma@latest