Merge branch 'main' into mhartington/DA-5233-hono-guide

ankur-arch · web-flow · commit 2cc25c36fea7 · 2025-10-09T14:20:14.000+06:00
diff --git a/.coderabbit.yaml b/.coderabbit.yaml
@@ -0,0 +1,23 @@
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
+# yaml template to refer to https://docs.coderabbit.ai/reference/yaml-template#enterprise
+language: "en-US"
+reviews:
+  collapse_walkthrough: false
+  profile: "chill"
+  high_level_summary: true
+  request_changes_workflow: true
+  poem: false
+  in_progress_fortune: false
+  sequence_diagrams: false
+  suggested_labels: false
+  suggested_reviewers: false
+  auto_review:
+    enabled: true
+    drafts: false
+  finishing_touches:
+    docstrings:
+      enabled: false
+    unit_tests:
+      enabled: false
+chat:
+  art: false
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-cockroachdb.mdx
@@ -5,7 +5,7 @@ metaTitle: 'Start from scratch with Prisma ORM using JavaScript and CockroachDB
 metaDescription: 'Learn how to create a new Node.js project from scratch by connecting Prisma ORM to your CockroachDB database and generating a Prisma Client for database access.'
 hide_table_of_contents: true
 langSwitcher: ['typescript', 'node']
-dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb', 'prismaPostgres']
+dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb']
 sidebar_custom_props: { badge: '15 min' }
 sidebar_class_name: hidden-sidebar
 pagination_next: getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-node-cockroachdb
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx
@@ -5,7 +5,7 @@ metaTitle: 'Start from scratch with Prisma ORM using JavaScript and MySQL (15 mi
 metaDescription: 'Learn how to create a new Node.js project from scratch by connecting Prisma ORM to your MySQL database and generating a Prisma Client for database access.'
 hide_table_of_contents: true
 langSwitcher: ['typescript', 'node']
-dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb', 'prismaPostgres']
+dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb']
 sidebar_custom_props: { badge: '15 min' }
 sidebar_class_name: hidden-sidebar
 pagination_next: getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-node-mysql
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx
@@ -5,7 +5,7 @@ metaTitle: 'Start from scratch with Prisma ORM using JavaScript and PlanetScale
 metaDescription: 'Learn how to create a new Node.js project from scratch by connecting Prisma ORM to your PlanetScale database and generating a Prisma Client for database access.'
 hide_table_of_contents: true
 langSwitcher: ['typescript', 'node']
-dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb', 'prismaPostgres']
+dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb']
 sidebar_custom_props: { badge: '15 min' }
 sidebar_class_name: hidden-sidebar
 pagination_next: getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-node-planetscale
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx
@@ -5,7 +5,7 @@ metaTitle: 'Start from scratch with Prisma ORM using JavaScript and PostgreSQL (
 metaDescription: 'Learn how to create a new Node.js project from scratch by connecting Prisma ORM to your PostgreSQL database and generating a Prisma Client for database access.'
 hide_table_of_contents: true
 langSwitcher: ['typescript', 'node']
-dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb', 'prismaPostgres']
+dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb']
 sidebar_custom_props: { badge: '15 min' }
 sidebar_class_name: hidden-sidebar
 pagination_next: getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-node-postgresql
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx
@@ -5,7 +5,7 @@ metaTitle: 'Start from scratch with Prisma ORM using JavaScript and SQL Server (
 metaDescription: 'Learn how to create a new Node.js project from scratch by connecting Prisma ORM to your SQL Server database and generating a Prisma Client for database access.'
 hide_table_of_contents: true
 langSwitcher: ['typescript', 'node']
-dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb', 'prismaPostgres']
+dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb']
 sidebar_custom_props: { badge: '15 min' }
 sidebar_class_name: hidden-sidebar
 pagination_next: getting-started/setup-prisma/start-from-scratch/relational-databases/connect-your-database-node-sqlserver
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-prismaPostgres.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-prismaPostgres.mdx
@@ -4,7 +4,7 @@ sidebar_label: 'Relational databases'
 metaTitle: 'Start from scratch with Prisma ORM using TypeScript and Prisma Postgres (15 min)'
 metaDescription: 'Learn how to create a new TypeScript project from scratch by connecting Prisma ORM to your Prisma Postgres database and generating a Prisma Client for database access.'
 hide_table_of_contents: true
-langSwitcher: ['typescript', 'node']
+langSwitcher: ['typescript']
 dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb', 'prismaPostgres']
 sidebar_custom_props: { badge: '15 min' }
 sidebar_class_name: hidden-sidebar
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-prismaPostgres.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-prismaPostgres.mdx
@@ -3,7 +3,7 @@ title: 'Connect your database using TypeScript and Prisma Postgres'
 sidebar_label: 'Connect your database'
 metaTitle: 'Connect your database using TypeScript and Prisma Postgres'
 metaDescription: 'Connect your database to your project using TypeScript and Prisma Postgres'
-langSwitcher: ['typescript', 'node']
+langSwitcher: ['typescript']
 dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb', 'prismaPostgres']
 sidebar_class_name: 'hidden-sidebar tech-switch'
 hide_table_of_contents: true
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-prismaPostgres.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-prismaPostgres.mdx
@@ -3,7 +3,7 @@ title: 'Using Prisma Migrate with TypeScript and Prisma Postgres'
 sidebar_label: 'Using Prisma Migrate'
 metaTitle: 'Using Prisma Migrate with TypeScript and Prisma Postgres'
 metaDescription: 'Create database tables with Prisma Migrate using TypeScript and Prisma Postgres'
-langSwitcher: ['typescript', 'node']
+langSwitcher: ['typescript']
 sidebar_class_name: hidden-sidebar
 dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb', 'prismaPostgres']
 hide_table_of_contents: true
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-prismaPostgres.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-prismaPostgres.mdx
@@ -3,7 +3,7 @@ title: 'Install Prisma Client (TypeScript and Prisma Postgres)'
 sidebar_label: 'Install Prisma Client'
 metaTitle: 'Install Prisma Client: TypeScript and Prisma Postgres'
 metaDescription: 'Install and generate Prisma Client in your project using TypeScript and Prisma Postgres'
-langSwitcher: ['typescript', 'node']
+langSwitcher: ['typescript']
 dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb', 'prismaPostgres']
 sidebar_class_name: hidden-sidebar
 hide_table_of_contents: true
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-prismaPostgres.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-prismaPostgres.mdx
@@ -3,7 +3,7 @@ title: 'Querying the database using TypeScript and Prisma Postgres'
 sidebar_label: 'Querying the database'
 metaTitle: 'Querying the database using TypeScript and Prisma Postgres'
 metaDescription: 'Write data to and query the database using TypeScript and Prisma Postgres'
-langSwitcher: ['typescript', 'node']
+langSwitcher: ['typescript']
 dbSwitcher: ['postgresql', 'mysql', 'sqlserver', 'planetscale', 'cockroachdb', 'prismaPostgres']
 hide_table_of_contents: true
 sidebar_class_name: hidden-sidebar
diff --git a/content/200-orm/100-prisma-schema/10-overview/02-data-sources.mdx b/content/200-orm/100-prisma-schema/10-overview/02-data-sources.mdx
@@ -4,8 +4,6 @@ metaTitle: 'Data sources (Reference)'
 metaDescription: 'Data sources enable Prisma to connect to your database. This page explains how to configure data sources in your Prisma schema.'
 ---
 
-<TopBlock>
-
 A data source determines how Prisma ORM connects to your database, and is represented by the [`datasource`](/orm/reference/prisma-schema-reference#datasource) block in the Prisma schema. The following data source uses the `postgresql` provider and includes a connection URL:
 
 ```prisma
@@ -22,8 +20,6 @@ A Prisma schema can only have _one_ data source. However, you can:
 
 > **Note**: Multiple provider support was removed in 2.22.0. Please see [Deprecation of provider array notation](https://github.com/prisma/prisma/issues/3834) for more information.
 
-</TopBlock>
-
 ## Securing database connections
 
 Some data source `provider`s allow you to configure your connection with SSL/TLS, and provide parameters for the `url` to specify the location of certificates.
diff --git a/content/200-orm/100-prisma-schema/10-overview/03-generators.mdx b/content/200-orm/100-prisma-schema/10-overview/03-generators.mdx
@@ -92,7 +92,7 @@ If you use macOS ARM64 (`darwin-arm64`), then the binary file that was compiled
 
 The new `prisma-client` generator offers greater control and flexibility when using Prisma ORM across different JavaScript environments (such as ESM, Bun, Deno, ...).
 
-It generates Prisma Client into a custom directory in your application's codebase that's specified via the `output` field on the `generator` block. This gives you full visibility and control over the generated code. It also [splits](#output-splitting-and-importing-types) the generated Prisma Client library into multiple files.
+It generates Prisma Client into a custom directory in your application's codebase that's specified via the `output` field on the `generator` block. This gives you full visibility and control over the generated code. It also [splits](#importing-types) the generated Prisma Client library into multiple files.
 
 This generator ensures you can bundle your application code exactly the way you want, without relying on hidden or automatic behaviors.
 
@@ -237,23 +237,12 @@ Below are the options for the `prisma-client` generator:
 
 :::
 
-### Output splitting and importing types
+### Importing types
 
-The `prisma-client-js` generator used to generate all typings into a single `index.d.ts` file, which could lead to [slowing down editors](https://github.com/prisma/prisma/issues/4807) (e.g. breaking auto-complete) with large schemas.
+The new `prisma-client` generator creates individual `.ts` files which allow for a more fine granular import of types. This can improve compile and typecheck performance and be useful for tree-shaking, too. 
+You can still use the top level barrel files that export all types through a single import.
 
-The new `prisma-client` generator now splits the generated Prisma Client library into multiple files and thus avoids the problems of a single, large output file.
-
-**Before** (`prisma-client-js`)
-
-```
-generated/
-└── prisma
-    ├── client.ts
-    ├── index.ts # -> this is split into multiple files in 6.7.0
-    └── libquery_engine-darwin.dylib.node
-```
-
-**After** (`prisma-client`)
+The overall structure of the generated output looks like this:
 
 ```
 generated/
@@ -263,15 +252,127 @@ generated/
     ├── commonInputTypes.ts
     ├── enums.ts
     ├── internal
-    │   ├── class.ts
-    │   ├── prismaNamespace.ts
-    │   └── prismaNamespaceBrowser.ts
+    │   ├── ...
     ├── models
     │   ├── Post.ts
     │   └── User.ts
     └── models.ts
 ```
 
+#### `client.ts`
+
+For use in your server code. 
+
+- Provides access to the `PrismaClient` instance and all model and utility types. 
+- Provides best compatibility with the `prisma-client-js` generated output.
+- Contains transitive dependencies on server only-packages, so cannot be used in browser contexts.
+
+Example:
+
+```ts
+import { Prisma, type Post, PrismaClient } from "./generated/prisma/client"
+```
+
+#### `browser.ts`
+
+For using types in your frontend (i.e. code that runs in the browser). 
+
+- Contains no transitive dependencies on Node.js or other server-only packages. 
+- Contains no real `PrismaClient` constructor.
+- Contains all model and enum types and values.
+- Provides access to various utilities like `Prisma.JsonNull` and `Prisma.Decimal`.
+- Available since `v6.16.0`.
+
+:::note
+
+The old `prisma-client-js` generator created a `node_modules` package and used export maps to dynamically provide a browser compatible export of the generated Prisma Client library. As the new `prisma-client` generator creates direct TypeScript source code and no `package.json` file anymore, this approach is not possible. Hence you need to be explicit about your imports and whether things run on server or client! 
+
+You can still wrap the generated code in a package and use a similar approach as with `prisma-client-js` on your own.
+
+:::
+
+Example:
+
+```ts
+import { Prisma, type Post } from "./generated/prisma/browser"
+```
+
+#### `enums.ts`
+
+Isolated access to user defined enum types and values.
+
+- Contains no transitive dependencies and is very slim.
+- Can be used on backend and frontend.
+- Prefer this for optimal tree shaking and typecheck performance when accessing enums.
+
+Example:
+
+```ts
+import { MyEnum } from "./generated/prisma/enums"
+```
+
+#### `models.ts`
+
+Isolated access to all model types.
+
+- Can be used on backend and frontend.
+- Contains all models including their derived utility types like `<ModelName>WhereInput` or `<ModelName>UpdateInput>`.
+
+:::note
+
+Plain model types are exposed here as `<ModelName>Model` (e.g. `PostModel`). This is in contrast to the exposed name in `client.ts` and `browser.ts` which is simply `<ModelName>` (e.g. `Post`).
+
+This is necessary due to internal constraints to avoid potential naming conflicts with internal types.
+
+:::
+
+Example:
+
+```ts
+import type { UserModel, PostModel, PostWhereInput, UserUpdateInput } from "./generated/prisma/models"
+```
+
+
+#### `models/<ModelName>.ts`
+
+Isolated access to the types for an individual model.
+
+- Can be used on backend and frontend.
+- Contains the models including its derived utility types like `<ModelName>WhereInput` or `<ModelName>UpdateInput>`.
+
+:::note
+
+The plain model type is exposed here as `<ModelName>Model` (e.g. `PostModel`).
+
+:::
+
+Example:
+
+```ts
+import type { UserModel, UserWhereInput, UserUpdateInput } from "./generated/prisma/models/User"
+```
+
+
+#### `commonInputTypes.ts`
+
+Provides shared utility types that you should rarely directly need.
+
+Example: 
+
+```ts
+import type { IntFilter } from "./generated/prisma/commonInputTypes"
+```
+
+#### `internal/*`
+
+:::warning
+
+Do not directly import from these files! They are not part of the stable API of the generated code and can change at any time in breaking ways.
+
+Usually anything you might need from there is exposed via `browser.ts` or `client.ts` under the `Prisma` namespace.
+
+:::
+
 ### Breaking changes from `prisma-client-js`
 
 - Requires an `output` path on the `generator` block
diff --git a/content/200-orm/500-reference/050-prisma-client-reference.mdx b/content/200-orm/500-reference/050-prisma-client-reference.mdx
@@ -929,7 +929,7 @@ prisma:query COMMIT
 | -------------------------- | ------------------------------ | --------------------------------------------------------------- |
 | JavaScript object (typed)  | `User`                         |                                                                 |
 | JavaScript object (plain)  | `{ name: "Alice Wonderland" }` | Use `select` and `include` to determine which fields to return. |
-| `RecordNotFound` exception |                                | Exception is thrown if record does not exist.                   |
+| `PrismaClientKnownRequestError` (code `P2025`) |                                | Thrown if the record to update does not exist. See [Error reference](/orm/reference/error-reference#p2025)                   |
 
 #### Remarks
 
@@ -1184,7 +1184,7 @@ To delete records that match a certain criteria, use [`deleteMany`](#deletemany)
 | -------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------- |
 | JavaScript object (typed)  | `User`                         | The `User` record that was deleted.                                                                           |
 | JavaScript object (plain)  | `{ name: "Alice Wonderland" }` | Data from the `User` record that was deleted. Use `select` and `include` to determine which fields to return. |
-| `RecordNotFound` exception |                                | Throws an exception if record does not exist.                                                                 |
+| `PrismaClientKnownRequestError` (code `P2025`) |                                | Thrown if the record to delete does not exist. See [Error reference](/orm/reference/error-reference#p2025)                   |                                                               |
 
 #### Remarks
 
diff --git a/content/200-orm/500-reference/325-prisma-config-reference.mdx b/content/200-orm/500-reference/325-prisma-config-reference.mdx
@@ -55,11 +55,12 @@ Here is a simplified version of the `PrismaConfig` type:
 
 ```ts
 export declare type PrismaConfig = {
+
   // Whether features with an unstable API are enabled.
   experimental: {
-    adapter: true,
-    externalTables: true,
-    studio: true,
+    adapter: boolean;
+    externalTables: boolean;
+    studio: boolean;
   },
 
   // The path to the schema file, or path to a folder that shall be recursively searched for *.prisma files.
@@ -68,7 +69,7 @@ export declare type PrismaConfig = {
   // The Driver Adapter used for Prisma CLI.
   adapter?: () => Promise<SqlMigrationAwareDriverAdapterFactory>;
 
-  // The configuration for Prisma Studio.
+  // Configuration for Prisma Studio.
   studio?: {
     adapter: () => Promise<SqlMigrationAwareDriverAdapterFactory>;
   };
@@ -89,6 +90,7 @@ export declare type PrismaConfig = {
   typedSql?: {
     path: string;
   };
+  
 };
 ```
 
@@ -486,4 +488,4 @@ You can specify a custom location for your config file when running Prisma CLI c
 
 ```terminal
 prisma validate --config ./path/to/myconfig.ts
-```
+```
diff --git a/content/250-postgres/100-introduction/200-getting-started.mdx b/content/250-postgres/100-introduction/200-getting-started.mdx
@@ -54,12 +54,11 @@ prisma generate --no-engine
 You can access Prisma Postgres with any ORM or database tool of your choice via [direct TCP connections](/postgres/database/direct-connections).
 
 In order to get a direct TCP connection string, you need to:
-1. open a project in your [Prisma Console](https://console.prisma.io) account (or create a new one)
-1. navigate to a environment with an active Prisma Postgres instance
-1. click the **API Keys** tab in the project's sidenav
-1. click the **Create API key** button 
-1. in the popup, provide a **Name** for the API key and click **Create**
-1. copy the connection string starting with `postgres://`, this is your direct TCP connection string
+1. Navigate to your active Prisma Postgres instance.
+1. Click the **API Keys** tab in the project's sidenav.
+1. Click the **Create API key** button.
+1. In the popup, provide a **Name** for the API key and click **Create**.
+1. Copy the connection string starting with `postgres://`, this is your direct connection string.
 
 Once you have the connection string, you can follow the setup docs for PostgreSQL of any ORM or database tool:
 
diff --git a/content/250-postgres/100-introduction/250-overview.mdx b/content/250-postgres/100-introduction/250-overview.mdx
@@ -11,8 +11,21 @@ toc: true
 
 It supports the following workflows:
 
-- Schema migrations and queries (via [Prisma ORM](https://www.prisma.io/orm))
+- Schema migrations and queries (via [Prisma ORM](https://www.prisma.io/orm) or any other ORM/database library)
 - Connection pooling and caching (via [Prisma Accelerate](https://www.prisma.io/accelerate))
+- Local database workflows via [`prisma dev`](/postgres/database/local-development)
+
+## Usage metrics
+
+You can view the following usage metrics in your Console Dashboard:
+
+- Key metrics
+    - Estimated upcoming invoice
+    - Total storage used
+    - Total DBs
+- Overall usage
+    - Cumulative operations
+    - Operations per day
 
 ## Billing 
 
diff --git a/content/250-postgres/300-database/650-direct-connections.mdx b/content/250-postgres/300-database/650-direct-connections.mdx
diff --git a/src/components/shortcodes/styles.module.scss b/src/components/shortcodes/styles.module.scss
