docs(prisma): Match docs to our Prisma v7 implementation (#1396)

Author: Tobbe

docs/docs/auth/dbauth.md

@@ -485,8 +485,11 @@ datasource db {
 }
 
 generator client {
-  provider      = "prisma-client-js"
-  binaryTargets = "native"
+  provider               = "prisma-client"
+  output                 = "./generated/prisma"
+  moduleFormat           = "cjs"
+  generatedFileExtension = "mts"
+  importFileExtension    = "mts"
 }
 
 model User {

docs/docs/cli-commands.md

@@ -1643,13 +1643,13 @@ If you look at your Prisma config file at `prisma.config.cjs`, you'll notice a
 `seed` definition:
 
 ```js
-{
+module.exports = defineConfig({
   // ...
-  "migrations": {
-    "seed": "yarn cedar exec seed"
-    // ...
+  migrations: {
+    path: 'db/migrations',
+    seed: 'yarn cedar exec seed',
   },
-}
+  // ...
 ```
 
 Prisma runs any command found in the `seed` setting when seeding via `yarn cedar prisma db seed` or `yarn cedar prisma migrate reset`.

docs/docs/database-seeds.md

@@ -90,7 +90,7 @@ Getting the right types for Prisma models can be tricky, but here's the formula:
 ```javascript title="scripts/seed.ts"
 import { db } from 'api/src/lib/db'
 // highlight-next-line
-import type { Prisma } from '@prisma/client'
+import type { Prisma } from 'api/db/generated/prisma/client.mts'
 
 export default async () => {
   try {

docs/docs/deploy/introduction.md

@@ -77,7 +77,9 @@ yarn rw deploy baremetal [--first-run]
 
 ### 3. Prisma and Database
 
-Cedar uses Prisma for managing database access and migrations. The settings in `api/prisma/schema.prisma` must include the correct deployment database, e.g. postgresql, and the database connection string.
+Cedar uses Prisma for managing database access and migrations. The settings in
+`api/db/schema.prisma` must include the correct deployment database, e.g.
+postgresql.
 
 To use PostgreSQL in production, include this in your `schema.prisma`:
 
@@ -87,7 +89,7 @@ datasource db {
 }
 ```
 
-The `url` setting above accesses the database connection string via an environment variable, `DATABASE_URL`. Using env vars is the recommended method for both ease of development process as well as security best practices.
+The database URL is configured both in the Prisma config file (`api/prisma.config.cjs`) via the `datasource.url` option using `env('DATABASE_URL')` and in `api/src/lib/db.{ts,js}` when constructing the Prisma client. Using env vars is the recommended method for both ease of development process as well as security best practices.
 
 Whenever you make changes to your `schema.prisma`, you must run the following command:
 

docs/docs/how-to/sending-emails.md

@@ -226,7 +226,7 @@ And then in the users service we'll just create a dummy method to start with.
 ```ts title="users.ts"
 // ...
 
-import type { Prisma } from '@prisma/client'
+import type { Prisma } from 'api/db/generated/prisma/client.mts'
 
 // ...
 

docs/docs/how-to/test-in-github-actions.md

@@ -73,14 +73,17 @@ Here's a handy guide for how to [set it up locally](../local-postgres-setup). We
 
 On to the changes. Modify your `schema.prisma` file to look like this:
 
-```graphql title="api/db/prisma.schema"
+```graphql title="api/db/schema.prisma"
 datasource db {
   provider = "postgresql"
 }
 
 generator client {
-  provider      = "prisma-client-js"
-  binaryTargets = "native"
+  provider               = "prisma-client"
+  output                 = "./generated/prisma"
+  moduleFormat           = "cjs"
+  generatedFileExtension = "mts"
+  importFileExtension    = "mts"
 }
 
 model UserExample {

docs/docs/tutorial/chapter0/what-is-cedarjs.md

@@ -159,8 +159,11 @@ datasource db {
 }
 
 generator client {
-  provider      = "prisma-client-js"
-  binaryTargets = "native"
+  provider               = "prisma-client"
+  output                 = "./generated/prisma"
+  moduleFormat           = "cjs"
+  generatedFileExtension = "mts"
+  importFileExtension    = "mts"
 }
 
 model Testimonial {

docs/docs/tutorial/chapter1/file-structure.md

@@ -114,7 +114,7 @@ Within `api` there are four directories:
   - `schema.prisma` contains the database schema (tables and columns)
 
   After we add our first database table, there will also be a SQLite database
-  file named `dev.db` and a directory called `migrations` created for us.
+  file named `dev.db` (located at `api/db/dev.db`) and a directory called `migrations` created for us.
   `migrations` contains the files that act as snapshots of the database schema
   changing over time.
 

docs/docs/tutorial/chapter2/getting-dynamic.md

@@ -27,8 +27,11 @@ datasource db {
 }
 
 generator client {
-  provider      = "prisma-client-js"
-  binaryTargets = "native"
+  provider               = "prisma-client"
+  output                 = "./generated/prisma"
+  moduleFormat           = "cjs"
+  generatedFileExtension = "mts"
+  importFileExtension    = "mts"
 }
 
 // highlight-start

docs/docs/tutorial/chapter3/saving-data.md

@@ -10,8 +10,11 @@ datasource db {
 }
 
 generator client {
-  provider      = "prisma-client-js"
-  binaryTargets = "native"
+  provider               = "prisma-client"
+  output                 = "./generated/prisma"
+  moduleFormat           = "cjs"
+  generatedFileExtension = "mts"
+  importFileExtension    = "mts"
 }
 
 model Post {