From 99ffc682101d5158e44420f3b14dcab29e6721f8 Mon Sep 17 00:00:00 2001 From: Ankur Datta <64993082+ankur-arch@users.noreply.github.com> Date: Thu, 17 Sep 2026 16:50:07 +0200 Subject: [PATCH 1/2] docs: show the config file that prisma init actually writes on the v7 quickstarts The Prisma ORM 7 quickstart and add-to-existing-project pages said `prisma init` creates `prisma.config.ts` with `env("DATABASE_URL")` from `prisma/config`. Running `npx prisma@prev init` (prisma 7.10.0) in a clean directory writes `prisma7.config.ts` with the generator comment, no `env` import, and `url: process.env["DATABASE_URL"]`. Prisma 7.9 still wrote `prisma.config.ts`. The fifteen pages pinned to `prisma@prev` now show the file as generated and carry a note about the rename. The two MongoDB pages are pinned to prisma 6.19.3 and are left as they are. Closes #7818 Co-Authored-By: Claude Fable 5.1 --- .../add-to-existing-project/cockroachdb.mdx | 18 +++++++++++++----- .../add-to-existing-project/mysql.mdx | 18 +++++++++++++----- .../add-to-existing-project/planetscale.mdx | 18 +++++++++++++----- .../add-to-existing-project/postgresql.mdx | 18 +++++++++++++----- .../prisma-postgres.mdx | 18 +++++++++++++----- .../add-to-existing-project/sql-server.mdx | 18 +++++++++++++----- .../add-to-existing-project/sqlite.mdx | 18 +++++++++++++----- .../v7/prisma-orm/quickstart/cockroachdb.mdx | 18 +++++++++++++----- .../(index)/v7/prisma-orm/quickstart/mysql.mdx | 18 +++++++++++++----- .../v7/prisma-orm/quickstart/planetscale.mdx | 18 +++++++++++++----- .../v7/prisma-orm/quickstart/postgresql.mdx | 18 +++++++++++++----- .../prisma-orm/quickstart/prisma-postgres.mdx | 18 +++++++++++++----- .../v7/prisma-orm/quickstart/sql-server.mdx | 18 +++++++++++++----- .../v7/prisma-orm/quickstart/sqlite.mdx | 18 +++++++++++++----- .../prisma-postgres/quickstart/prisma-orm.mdx | 18 +++++++++++++----- 15 files changed, 195 insertions(+), 75 deletions(-) diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/cockroachdb.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/cockroachdb.mdx index 71e3650e89..8275ae86e7 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/cockroachdb.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/cockroachdb.mdx @@ -40,13 +40,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection configuration - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -54,11 +56,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/mysql.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/mysql.mdx index 81d4db9e1e..11690626f2 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/mysql.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/mysql.mdx @@ -38,13 +38,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection configuration - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -52,11 +54,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/planetscale.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/planetscale.mdx index f7e8f7a925..06e7e68f96 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/planetscale.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/planetscale.mdx @@ -48,13 +48,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection configuration - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -62,11 +64,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" tab="MySQL" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/postgresql.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/postgresql.mdx index 3fe0727a90..7339347d58 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/postgresql.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/postgresql.mdx @@ -40,13 +40,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection configuration - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -54,11 +56,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/prisma-postgres.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/prisma-postgres.mdx index 836d20c493..66dd41257a 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/prisma-postgres.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/prisma-postgres.mdx @@ -40,13 +40,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection configuration - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -54,11 +56,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/sql-server.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/sql-server.mdx index b200303f22..8a2259b0fe 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/sql-server.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/sql-server.mdx @@ -39,13 +39,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection configuration - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -53,11 +55,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/sqlite.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/sqlite.mdx index d03d75fec1..ac8aa1b260 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/sqlite.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/add-to-existing-project/sqlite.mdx @@ -39,13 +39,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection configuration - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -53,11 +55,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/cockroachdb.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/cockroachdb.mdx index e9c1102507..6e70a12fa8 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/cockroachdb.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/cockroachdb.mdx @@ -92,13 +92,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection and schema models - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -106,11 +108,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/mysql.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/mysql.mdx index f280875eaa..f909bd2043 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/mysql.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/mysql.mdx @@ -96,13 +96,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection and schema models - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -110,11 +112,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/planetscale.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/planetscale.mdx index 38aa576e92..49b1d35ebe 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/planetscale.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/planetscale.mdx @@ -102,13 +102,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection and schema models - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -116,11 +118,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" tab="MySQL" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/postgresql.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/postgresql.mdx index cb70b57d56..e44d174cfe 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/postgresql.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/postgresql.mdx @@ -98,13 +98,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection and schema models - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -112,11 +114,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/prisma-postgres.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/prisma-postgres.mdx index d35ec43ae2..738dce0d40 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/prisma-postgres.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/prisma-postgres.mdx @@ -91,13 +91,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection and schema models - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -105,11 +107,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/sql-server.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/sql-server.mdx index 016dd81e00..bca9e5ddb9 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/sql-server.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/sql-server.mdx @@ -92,13 +92,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection and schema models - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -106,11 +108,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/sqlite.mdx b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/sqlite.mdx index 1658bea7c7..13ed213c72 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/sqlite.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-orm/quickstart/sqlite.mdx @@ -96,13 +96,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection and schema models - Creates a `.env` file in the root directory for environment variables -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -110,11 +112,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" diff --git a/apps/docs/content/docs/(index)/v7/prisma-postgres/quickstart/prisma-orm.mdx b/apps/docs/content/docs/(index)/v7/prisma-postgres/quickstart/prisma-orm.mdx index 8f33b4e781..a25ca16216 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-postgres/quickstart/prisma-orm.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-postgres/quickstart/prisma-orm.mdx @@ -72,13 +72,15 @@ This command does a few things: - Creates a `prisma/` directory with a `schema.prisma` file containing your database connection and schema models - Creates a `.env` file in the root directory for environment variables - Generates the Prisma Client in the `generated/prisma/` directory -- Creates a `prisma.config.ts` file for Prisma configuration +- Creates a `prisma7.config.ts` file for Prisma configuration -The generated `prisma.config.ts` file looks like this: +The generated `prisma7.config.ts` file looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -86,11 +88,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + The generated schema uses [the ESM-first `prisma-client` generator](/orm/v7/prisma-schema/overview/generators#prisma-client) with a custom output path: ```prisma title="prisma/schema.prisma" From 9cb33f9f8f4f62b58d27aca19641366c5c707baa Mon Sep 17 00:00:00 2001 From: "reviewer (Program)" Date: Thu, 17 Sep 2026 15:23:16 +0000 Subject: [PATCH 2/2] docs: show prisma7.config.ts on the Prisma Postgres from-the-cli page too The page is pinned to prisma@prev like the other fifteen v7 quickstart pages but still showed prisma init writing prisma.config.ts with env(), and its Studio command passed --config ./prisma.config.ts, a file init no longer writes. Now shows the generated prisma7.config.ts, the rename note, and points --config at it. --- .../v7/prisma-postgres/from-the-cli.mdx | 22 +++++++++++++------ 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/apps/docs/content/docs/(index)/v7/prisma-postgres/from-the-cli.mdx b/apps/docs/content/docs/(index)/v7/prisma-postgres/from-the-cli.mdx index 20950548d0..6676db23a5 100644 --- a/apps/docs/content/docs/(index)/v7/prisma-postgres/from-the-cli.mdx +++ b/apps/docs/content/docs/(index)/v7/prisma-postgres/from-the-cli.mdx @@ -26,7 +26,7 @@ Once these commands have terminated: - The `prisma/` folder was created with an empty `schema.prisma` file. - The `DATABASE_URL` env var was set in a `.env` file. -- The `prisma.config.ts` file was created with the default configuration. +- The `prisma7.config.ts` file was created with the default configuration. - You have a Prisma Postgres connection string to paste into `.env`. ## 1. Organize your project directory @@ -120,13 +120,15 @@ Here's what each package does: - **`@types/pg`** - TypeScript type definitions for node-postgres - **`dotenv`** - Loads environment variables from your `.env` file -### 2.4. Review the generated prisma.config.ts +### 2.4. Review the generated prisma7.config.ts -The `prisma init` command automatically created a `prisma.config.ts` file that looks like this: +The `prisma init` command automatically created a `prisma7.config.ts` file that looks like this: -```typescript title="prisma.config.ts" +```typescript title="prisma7.config.ts" +// This file was generated by Prisma, and assumes you have installed the following: +// npm install --save-dev prisma dotenv import "dotenv/config"; -import { defineConfig, env } from "prisma/config"; +import { defineConfig } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", @@ -134,11 +136,17 @@ export default defineConfig({ path: "prisma/migrations", }, datasource: { - url: env("DATABASE_URL"), + url: process.env["DATABASE_URL"], }, }); ``` +:::note + +Prisma ORM 7.10 and later name this file `prisma7.config.ts` so that it does not clash with the Prisma 8 config format, which only accepts `prisma.config.ts`. The Prisma 7 CLI discovers either name, so a project that already has a `prisma.config.ts` keeps working. + +::: + ### 2.5. Create a script to query the database Create an `index.ts` file in the root directory, this will be used to query your application with Prisma ORM: @@ -449,7 +457,7 @@ This page covered a basic Prisma Postgres setup. The [Quickstart](/v7/prisma-orm Prisma ORM comes with a built-in GUI to view and edit the data in your database. You can open it using the following command: ```npm -npx prisma studio --config ./prisma.config.ts +npx prisma studio --config ./prisma7.config.ts ``` With Prisma Postgres, you can also directly use Prisma Studio inside the [Console](https://console.prisma.io) by selecting the **Studio** tab in your project.