diff --git a/apps/blog/content/blog/building-the-stack-for-the-next-million-products/index.mdx b/apps/blog/content/blog/building-the-stack-for-the-next-million-products/index.mdx deleted file mode 100644 index 022c9fde9f..0000000000 --- a/apps/blog/content/blog/building-the-stack-for-the-next-million-products/index.mdx +++ /dev/null @@ -1,138 +0,0 @@ ---- -title: "Prisma Is Building the Stack for the Next Million Products" -slug: "building-the-stack-for-the-next-million-products" -date: "2026-08-25" -authors: - - "Søren Bramer Schmidt" -metaTitle: "Prisma Is Building the Stack for the Next Million Products" -metaDescription: "Prisma is building a software factory: one environment where a builder describes what they want and an agent builds it, runs it, inspects it, fixes it, and keeps going. Prisma ORM, Prisma Postgres, and Prisma Compute, connected into one loop." -excerpt: "We are building a software factory: one environment where a builder can describe what they want and an agent can build it, run it, inspect it, fix it, and keep going." -heroImagePath: "/building-the-stack-for-the-next-million-products/imgs/hero.svg" -heroImageAlt: "The shortest path from an idea to working software: a request card, a short path through build, deploy and iterate, and a running application showing a usage limit warning." -metaImagePath: "/building-the-stack-for-the-next-million-products/imgs/meta.png" -pinned: true -tags: - - "announcement" - - "platform" - - "ai" ---- - -**Prisma should give humans and agents the shortest path from an idea to working software.** - -Today that path is still broken across code, databases, deployment, logs, previews, and developer tooling. We want those pieces to behave like one system instead of a collection of hand-offs. - -That idea has been taking shape across Prisma for a while. [Prisma ORM](https://www.prisma.io/orm?utm_source=blog&utm_medium=blog&utm_campaign=prisma-rebrand-2026&utm_content=launch-post) simplified working with data. [Prisma Postgres](https://www.prisma.io/postgres?utm_source=blog&utm_medium=blog&utm_campaign=prisma-rebrand-2026&utm_content=launch-post) made isolated databases available on demand. [Prisma Compute](https://www.prisma.io/compute?utm_source=blog&utm_medium=blog&utm_campaign=prisma-rebrand-2026&utm_content=launch-post) gave applications a place to run. - -Together, they let builders and agents move from code changes to a running application without stitching the infrastructure together themselves. - -> The stack should fit inside the conversation. - -## Writing the code is easy now, shipping is still a challenge - -An agent can already write a feature surprisingly well. The harder part is getting that feature running in a real application. - -To do that, it needs a safe place to change data, somewhere to run the app, a way to deploy it, and enough visibility to understand what went wrong. Today, those pieces are spread across different products, so every handoff adds another API, credential, dashboard, and piece of context to recover. - -A coworker once described an agent as a very smart intern who joins for a day, reads everything, ships one feature, and then disappears forever. That stuck with me because it captures the problem well. - -You cannot assume the next agent remembers yesterday's work. The environment has to provide the right context while the work is happening, without forcing the agent to constantly rediscover the system. - -> Agents need to be able to access the information they need while they are working. - -That changes what good infrastructure looks like. - -## A feature should move through one continuous loop - -Consider a straightforward request: warn a customer before they reach their usage limit. - -You describe the outcome, the constraints, and the trade-offs. The agent reads the codebase and data model, changes the schema, implements the backend and UI, runs the application against an isolated database, and deploys a preview where it can exercise the feature against realistic state. - -During validation, the traces show that two concurrent requests can send the warning email twice. The agent fixes the race, runs the tests again, updates the preview, and checks the result before raising a pull request with a running environment and evidence that the change works. - -That is the unit of work we care about: a working change that has been built, run, observed, and validated. - -The Builder still owns the outcome, the judgment, and the trade-offs. The agent takes on more of the implementation and validation. Prisma provides the environment that lets the work continue without losing the thread. - -## Prisma is bringing that loop into one environment - -The pieces already let an agent move much further through the job before a human has to step in. - -Prisma Compute lets the agent run what it built. Prisma Postgres gives each task its own database. - -Prisma ORM 8 keeps database changes inside the feedback loop. - -### Prisma Compute lets the agent run what it built - -Once an agent has changed the code, it needs a real environment where it can run the application, exercise the feature, inspect the result, and keep iterating. [Prisma Compute](/launching-prisma-compute-public-beta) gives it that place. - -Compute runs [Bun on long-running servers](/bun-rust-rewrite-prisma-compute) with fast snapshot and restore, and it follows a [usage-based model](/price-the-work-not-the-workflow) so spinning up another environment can become part of the development loop instead of a separate infrastructure decision. - -The important change is that the agent no longer has to stop after producing code. - -### Prisma Postgres gives each task its own database - -The same principle applies to data. An agent working on a feature should not have to wait for someone to provision infrastructure or share a development database that everyone is afraid to touch. - -[Prisma Postgres](https://www.prisma.io/docs/postgres?utm_source=blog&utm_medium=blog&utm_campaign=prisma-rebrand-2026&utm_content=launch-post) can be created programmatically, so an agent or preview deployment can get an [isolated database for the work it is doing](/ship-risky-schema-changes-without-a-shared-staging-database). Databases pause and resume automatically, and you pay for the requests made, which makes temporary environments practical instead of expensive overhead. - -For the usage-limit feature, the agent can change the schema and test against realistic state without risking production data or colliding with somebody else's work. - -### Prisma ORM 8 keeps database changes inside the feedback loop - -The data model remains one of the most important pieces of context in an application, which is why Prisma ORM is still central to what we are building. - -[Prisma ORM 8](https://www.prisma.io/docs/orm/v8?utm_source=blog&utm_medium=blog&utm_campaign=prisma-rebrand-2026&utm_content=launch-post) gives agents faster, safer feedback as they change that model. [Safeguards and linting](/stop-your-ai-agent-dropping-your-database) can catch mistakes earlier and prevent destructive actions against a live database, while the ORM itself is [substantially faster than Prisma 7](/prisma-next-performance-benchmark) and is now implemented entirely in TypeScript. - -In practice, the agent can change the data model, get useful feedback, correct the problem, and continue working without waiting for a human to discover the mistake later. - -## The real product is the connected loop - -Compute, Postgres, and ORM are useful on their own, but the larger opportunity comes from removing the boundaries between them. - -A Builder should not need to manually provision a database every time an agent needs an isolated environment, copy connection strings between providers, teach each agent how another deployment platform works, or reconstruct the history of a feature from several unrelated dashboards. - -For an individual developer, that means an idea can get much further before infrastructure becomes the job. For a team, more work can arrive for review already running and already validated. For the agent, fewer system boundaries mean less context to reconstruct before it can continue. - -This is also why we care so much about coherence. Memory systems and "company brain" products can help agents recover context, but they are optimisations around a more basic requirement: the system itself should expose the right information at the moment the agent needs it. - -Over time, we plan to extend this environment with cloud agents, issue tracking, code hosting, and a tighter connection between operational data and the work that produced it. Logs, traces, errors, and customer behaviour should feed back into the next iteration so the next agent can see both the original intent and what actually happened in production. - -The goal is a shorter, more reliable path from deciding what to build to seeing it work and improving it again. - -## We are building this from our own experience - -This direction comes from [how our own way of building software has changed](/evolving-agentic-engineering-at-prisma) over the past year. - -At Prisma, we removed sprints and traditional teams. Most work no longer starts in an issue tracker, and [everyone is a Builder](/drive-and-the-maker) who can pick up the most important work in front of them. We are also a smaller company than we were twelve months ago, while engineering velocity, customer happiness, and revenue have all increased. - -AI is not the only reason for that change, but it has made one thing very clear: writing the code is becoming a much smaller part of the job. - -A feature might take twenty minutes to implement, but getting it into the hands of a user can still take much longer. You still need to provision infrastructure, deploy the application, test it in a real environment, inspect logs when something goes wrong, and make another change. - -That gap matters even more for agents. An agent can write the code quickly, but if it has to stop and wait for a human every time it needs a database, a deployment, a log, or a safe place to run the application, it cannot complete the job on its own. - -We do not think the answer is to teach agents how to navigate more tools, dashboards, and hand-offs. We think those steps should become part of one connected environment, so the agent can keep working from the initial idea all the way to a running, validated change. - -That is the stack we want to build. - -## Start building with Prisma Compute - -Prisma Compute is the newest step toward that vision. It works with the coding agents you already use, including Claude, Codex, and Composer, and comes with Prisma Postgres and [Object Storage](https://www.prisma.io/docs/storage?utm_source=blog&utm_medium=blog&utm_campaign=prisma-rebrand-2026&utm_content=launch-post) so you can give an agent a real project, let it build against real infrastructure, and run what it made. - - - -Or [start from the terminal](/introducing-create-prisma): - -```bash -npm create prisma@latest -``` - -For an existing project: - -```bash -npx prisma@latest init -``` - -There is more on the way. Follow us on [X](https://x.com/prisma) or join the [Discord](https://pris.ly/discord) to see the upcoming releases as they land. diff --git a/apps/blog/public/building-the-stack-for-the-next-million-products/imgs/hero.svg b/apps/blog/public/building-the-stack-for-the-next-million-products/imgs/hero.svg deleted file mode 100644 index 46689ab532..0000000000 --- a/apps/blog/public/building-the-stack-for-the-next-million-products/imgs/hero.svg +++ /dev/null @@ -1,64 +0,0 @@ - - Prisma Is Building the Stack for the Next Million Products - The shortest path from an idea to working software: a request card, Build, Deploy and Iterate tiles in a loop, and a running application showing a usage limit warning. Prisma blog cover, 2026 brand, paper surface with a prism cyan accent. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The shortest path - to working software - - diff --git a/apps/blog/public/building-the-stack-for-the-next-million-products/imgs/meta.png b/apps/blog/public/building-the-stack-for-the-next-million-products/imgs/meta.png deleted file mode 100644 index 5c4957c9bc..0000000000 Binary files a/apps/blog/public/building-the-stack-for-the-next-million-products/imgs/meta.png and /dev/null differ diff --git a/apps/docs/content/docs/(index)/index.mdx b/apps/docs/content/docs/(index)/index.mdx index 8183fd8cea..96721d7145 100644 --- a/apps/docs/content/docs/(index)/index.mdx +++ b/apps/docs/content/docs/(index)/index.mdx @@ -63,7 +63,7 @@ If you're using Express or another Node.js server, follow the [existing-project - + } /> @@ -124,7 +124,7 @@ Add Prisma ORM 7 to this project with my existing database. If I have not given you a database connection string and none exists in the project, stop and ask. -1. Run `npx prisma@7.9.1 init` (Prisma 7). For an existing database, set DATABASE_URL in `.env` and introspect it with `npx prisma db pull`; for a new schema, define models in `prisma/schema.prisma` and run `npx prisma migrate dev --name init`. If migrate dev asks to reset the database, stop and ask me first. +1. Run `npx prisma@7.10.0 init` (Prisma 7). For an existing database, set DATABASE_URL in `.env` and introspect it with `npx prisma db pull`; for a new schema, define models in `prisma/schema.prisma` and run `npx prisma migrate dev --name init`. If migrate dev asks to reset the database, stop and ask me first. 2. Install the driver adapter for the database (Prisma 7 requires one), e.g. `npm install @prisma/adapter-pg` for PostgreSQL, and pass it to `new PrismaClient({ adapter })`. Generate the client with `npx prisma generate` and write one query in an existing code path. 3. Run the query (e.g. with `npx tsx`) and show me the output, the schema, and the query you added. diff --git a/apps/docs/content/docs/(index)/v7/getting-started.mdx b/apps/docs/content/docs/(index)/v7/getting-started.mdx index 4866ee23b5..c45224e86b 100644 --- a/apps/docs/content/docs/(index)/v7/getting-started.mdx +++ b/apps/docs/content/docs/(index)/v7/getting-started.mdx @@ -6,7 +6,7 @@ metaTitle: Prisma 7 getting started metaDescription: 'Choose the fastest Prisma 7 setup path. Quickstarts and existing-project guides for Prisma ORM 7, Prisma Postgres, and Prisma Compute, plus an agent prompt.' --- -Prisma 7 remains fully supported; [Prisma 8](/getting-started) is the current release of Prisma ORM. Scaffold a new Prisma 7 app with `npx create-prisma@stable`, or add it to an existing project with `npx prisma@7.9.1 init`. This page collects the Prisma 7 starting points: start a new project, add Prisma to an existing one, then deploy. +Prisma 7 remains fully supported; [Prisma 8](/getting-started) is the current release of Prisma ORM. Scaffold a new Prisma 7 app with `npx create-prisma@stable`, or add it to an existing project with `npx prisma@7.10.0 init`. This page collects the Prisma 7 starting points: start a new project, add Prisma to an existing one, then deploy. :::note @@ -57,7 +57,7 @@ Set up the Prisma 7 stack: Prisma ORM 7, Prisma Postgres, and Prisma Compute. If I have not told you which framework template to use, stop and ask. -1. Scaffold a new app non-interactively: `npx create-prisma@stable --name my-app --template [next|hono|nuxt|astro|nest|svelte|tanstack-start|elysia|turborepo] --provider postgresql --no-deploy`. Or add Prisma 7 to an existing app with `npx prisma@7.9.1 init --db`, which provisions a Prisma Postgres database and may open a browser to sign in; if it does, stop and ask me to complete the sign-in. +1. Scaffold a new app non-interactively: `npx create-prisma@stable --name my-app --template [next|hono|nuxt|astro|nest|svelte|tanstack-start|elysia|turborepo] --provider postgresql --no-deploy`. Or add Prisma 7 to an existing app with `npx prisma@7.10.0 init --db`, which provisions a Prisma Postgres database and may open a browser to sign in; if it does, stop and ask me to complete the sign-in. 2. From the project directory, define a small schema in `prisma/schema.prisma`, then run `npx prisma migrate dev --name init` and `npx prisma generate`. If migrate dev asks to reset the database, stop and ask me first. 3. Update the seed and app code to query the schema, and verify locally with the dev script. 4. Deploy with Prisma Compute: port the app to Prisma Composer following https://www.prisma.io/docs/composer/porting-an-app.md — declare the service around the existing server, read the port from `service.port()` and bind 0.0.0.0, bind `DATABASE_URL` with `envSecret` in the service input, and produce one self-contained entry file. Check `npx prisma@latest auth whoami`. If I am not signed in, stop and ask me to run `npx prisma@latest auth login`, because that step opens a browser. Then run the build followed by `npx prisma@latest deploy module.ts` with `DATABASE_URL` exported so the first deploy copies it up, and verify the deployed URL with curl. 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 dcc00fac22..5a6f902493 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 @@ -15,8 +15,8 @@ metaDescription: 'Add Prisma ORM to an existing TypeScript project with Cockroac Navigate to your existing project directory and install the required dependencies: ```npm -npm install prisma@7.9.1 @types/node @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install prisma@7.10.0 @types/node @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` Here's what each package does: 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 b8b823f67e..e2d737dff9 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 @@ -15,8 +15,8 @@ metaDescription: 'Add Prisma ORM to an existing TypeScript project with MySQL an Navigate to your existing project directory and install the required dependencies: ```npm -npm install prisma@7.9.1 @types/node --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-mariadb dotenv +npm install prisma@7.10.0 @types/node --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-mariadb dotenv ``` Here's what each package does: 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 98e8879370..014f08c755 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 @@ -17,15 +17,15 @@ Navigate to your existing project directory and install the required dependencie ### MySQL ```npm -npm install prisma@7.9.1 @types/node --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-planetscale undici dotenv +npm install prisma@7.10.0 @types/node --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-planetscale undici dotenv ``` ### Postgres ```npm -npm install prisma@7.9.1 @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install prisma@7.10.0 @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` ## 2. Initialize Prisma ORM 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 0e61f438fc..7b74a432b3 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 @@ -15,8 +15,8 @@ metaDescription: 'Add Prisma ORM to an existing TypeScript project with PostgreS Navigate to your existing project directory and install the required dependencies: ```npm -npm install prisma@7.9.1 @types/node @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install prisma@7.10.0 @types/node @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` Here's what each package does: 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 72e24a2bbb..d4b2eb7c63 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 @@ -15,8 +15,8 @@ metaDescription: 'Add Prisma ORM to an existing TypeScript project with Prisma P Navigate to your existing project directory and install the required dependencies: ```npm -npm install prisma@7.9.1 @types/node @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install prisma@7.10.0 @types/node @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` Here's what each package does: 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 1f57ef44a3..2ebf8db636 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 @@ -15,8 +15,8 @@ metaDescription: 'Add Prisma ORM to an existing TypeScript project with SQL Serv Navigate to your existing project directory and install the required dependencies: ```npm -npm install prisma@7.9.1 @types/node @types/mssql --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-mssql dotenv +npm install prisma@7.10.0 @types/node @types/mssql --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-mssql dotenv ``` Here's what each package does: 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 87f1e976ba..724f59f22f 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 @@ -15,8 +15,8 @@ metaDescription: 'Add Prisma ORM to an existing TypeScript project with SQLite a Navigate to your existing project directory and install the required dependencies: ```npm -npm install prisma@7.9.1 @types/node @types/better-sqlite3 --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-better-sqlite3 dotenv +npm install prisma@7.10.0 @types/node @types/better-sqlite3 --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-better-sqlite3 dotenv ``` Here's what each package does: 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 c40ef346c7..25bf9181dc 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 @@ -36,8 +36,8 @@ npx tsc --init Install the packages needed for this quickstart: ```npm -npm install prisma@7.9.1 @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install prisma@7.10.0 @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` Here's what each package does: 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 c15a127f40..5b14210975 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 @@ -42,8 +42,8 @@ npx tsc --init Install the packages needed for this quickstart: ```npm -npm install prisma@7.9.1 @types/node --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-mariadb dotenv +npm install prisma@7.10.0 @types/node --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-mariadb dotenv ``` Here's what each package does: 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 fc484f4781..6a287416f6 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 @@ -40,15 +40,15 @@ Install the packages needed for this quickstart: ### MySQL ```npm -npm install prisma@7.9.1 --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-planetscale undici dotenv +npm install prisma@7.10.0 --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-planetscale undici dotenv ``` ### Postgres ```npm -npm install prisma@7.9.1 @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install prisma@7.10.0 @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` ## 3. Configure ESM support 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 e5481c61f8..47c8fe6d1f 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 @@ -42,8 +42,8 @@ npx tsc --init Install the packages needed for this quickstart: ```npm -npm install prisma@7.9.1 @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install prisma@7.10.0 @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` Here's what each package does: 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 7287c771ca..5b56676773 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 @@ -33,8 +33,8 @@ npx tsc --init Install the packages needed for this quickstart: ```npm -npm install prisma@7.9.1 @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install prisma@7.10.0 @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` Here's what each package does: 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 d24db18ec3..1e593765fe 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 @@ -37,8 +37,8 @@ npx tsc --init Install the packages needed for this quickstart: ```npm -npm install prisma@7.9.1 @types/node @types/mssql --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-mssql dotenv +npm install prisma@7.10.0 @types/node @types/mssql --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-mssql dotenv ``` Here's what each package does: 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 d00c53ce24..dfc4f3c419 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 @@ -34,11 +34,11 @@ npx tsc --init Install the packages needed for this quickstart: ```npm -npm install prisma@7.9.1 @types/node @types/better-sqlite3 -D +npm install prisma@7.10.0 @types/node @types/better-sqlite3 -D ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-better-sqlite3 dotenv +npm install @prisma/client@7.10.0 @prisma/adapter-better-sqlite3 dotenv ``` :::note[pnpm users with SQLite] 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 cc20c6434f..2463a53ea3 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 @@ -17,7 +17,7 @@ This page provides a step-by-step guide for Prisma Postgres after setting it up This guide assumes you initialized Prisma with `prisma init` and created a Prisma Postgres database with `npx create-db`: ```npm -npx prisma@7.9.1 init +npx prisma@7.10.0 init npx create-db ``` @@ -107,8 +107,8 @@ Update `package.json` to enable ESM: Install the required dependencies to use Prisma Postgres: ```npm -npm install prisma@7.9.1 --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install prisma@7.10.0 --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` Here's what each package does: 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 4590195737..199422c918 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 @@ -17,8 +17,8 @@ metaDescription: 'Set up Prisma Postgres in a new TypeScript project with Prisma Install the packages needed for this quickstart: ```npm -npm install prisma@7.9.1 @types/node --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv +npm install prisma@7.10.0 @types/node --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv ``` Here's what each package does: diff --git a/apps/docs/content/docs/ai/index.mdx b/apps/docs/content/docs/ai/index.mdx index b5b988da42..f235cc56c7 100644 --- a/apps/docs/content/docs/ai/index.mdx +++ b/apps/docs/content/docs/ai/index.mdx @@ -13,7 +13,7 @@ In the era of AI, where code is increasingly written by agents, ensuring clarity Run the following command to bootstrap your database with a prompt: ```npm -npx prisma@7.9.1 init --prompt "Create a habit tracker application" +npx prisma@7.10.0 init --prompt "Create a habit tracker application" ``` ## AI Coding Tools diff --git a/apps/docs/content/docs/ai/prompts/astro.mdx b/apps/docs/content/docs/ai/prompts/astro.mdx index 99f810f416..fe5d2c78c1 100644 --- a/apps/docs/content/docs/ai/prompts/astro.mdx +++ b/apps/docs/content/docs/ai/prompts/astro.mdx @@ -88,10 +88,10 @@ export default prisma ```bash # Dev dependencies -npm install prisma@7.9.1 tsx --save-dev +npm install prisma@7.10.0 tsx --save-dev # Production dependencies -npm install @prisma/extension-accelerate @prisma/client@7.9.1 +npm install @prisma/extension-accelerate @prisma/client@7.10.0 ``` ## CORRECT PRISMA INITIALIZATION diff --git a/apps/docs/content/docs/ai/prompts/nextjs.mdx b/apps/docs/content/docs/ai/prompts/nextjs.mdx index 6416972613..5aa4baf971 100644 --- a/apps/docs/content/docs/ai/prompts/nextjs.mdx +++ b/apps/docs/content/docs/ai/prompts/nextjs.mdx @@ -168,10 +168,10 @@ export default prisma ```bash # Dev dependencies -npm install prisma@7.9.1 tsx --save-dev +npm install prisma@7.10.0 tsx --save-dev # Production dependencies -npm install @prisma/adapter-pg @prisma/client@7.9.1 dotenv +npm install @prisma/adapter-pg @prisma/client@7.10.0 dotenv ``` ## CORRECT PRISMA INITIALIZATION @@ -428,11 +428,11 @@ User should follow these steps (AI should provide these instructions): 1. **Install dependencies**: ```npm - npm install prisma@7.9.1 tsx --save-dev + npm install prisma@7.10.0 tsx --save-dev ``` ```npm - npm install @prisma/adapter-pg @prisma/client@7.9.1 dotenv + npm install @prisma/adapter-pg @prisma/client@7.10.0 dotenv ``` 2. **Initialize Prisma, then create Prisma Postgres:** diff --git a/apps/docs/content/docs/ai/prompts/nuxt.mdx b/apps/docs/content/docs/ai/prompts/nuxt.mdx index d34fee7378..8c620cfb66 100644 --- a/apps/docs/content/docs/ai/prompts/nuxt.mdx +++ b/apps/docs/content/docs/ai/prompts/nuxt.mdx @@ -174,10 +174,10 @@ export { prisma } ```bash # Production dependencies -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv # Dev dependencies -npm install -D prisma@7.9.1 @types/pg tsx +npm install -D prisma@7.10.0 @types/pg tsx ``` ## CORRECT PRISMA INITIALIZATION @@ -440,11 +440,11 @@ User should follow these steps (AI should provide these instructions): 2. **Install dependencies**: ```bash - npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv + npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` ```bash - npm install -D prisma@7.9.1 @types/pg tsx + npm install -D prisma@7.10.0 @types/pg tsx ``` 3. **Initialize Prisma AND create Prisma Postgres database** (⚠️ USER MUST RUN MANUALLY): diff --git a/apps/docs/content/docs/ai/prompts/prisma-7.mdx b/apps/docs/content/docs/ai/prompts/prisma-7.mdx index 1b35fa0834..6a0bc16c09 100644 --- a/apps/docs/content/docs/ai/prompts/prisma-7.mdx +++ b/apps/docs/content/docs/ai/prompts/prisma-7.mdx @@ -72,8 +72,8 @@ alwaysApply: false ## 1) Dependencies - Upgrade/install: - - Dev: `prisma@7.9.1`, `tsx`, `dotenv` (skip if Bun). - - Runtime: `@prisma/client@7.9.1`. + - Dev: `prisma@7.10.0`, `tsx`, `dotenv` (skip if Bun). + - Runtime: `@prisma/client@7.10.0`. - **One** database adapter that matches the datasource: - Postgres: `@prisma/adapter-pg` - SQLite: `@prisma/adapter-better-sqlite3` diff --git a/apps/docs/content/docs/ai/prompts/turborepo.mdx b/apps/docs/content/docs/ai/prompts/turborepo.mdx index d78001ac1f..347395385f 100644 --- a/apps/docs/content/docs/ai/prompts/turborepo.mdx +++ b/apps/docs/content/docs/ai/prompts/turborepo.mdx @@ -122,8 +122,8 @@ At repo root: npm install turbo --save-dev # Prisma v7 -npm install prisma@7.9.1 tsx --save-dev -npm install @prisma/client@7.9.1 dotenv +npm install prisma@7.10.0 tsx --save-dev +npm install @prisma/client@7.10.0 dotenv ``` If using Prisma Postgres: diff --git a/apps/docs/content/docs/ai/tutorials/typefully-clone.mdx b/apps/docs/content/docs/ai/tutorials/typefully-clone.mdx index 3828f6817d..5e9ec4ad9f 100644 --- a/apps/docs/content/docs/ai/tutorials/typefully-clone.mdx +++ b/apps/docs/content/docs/ai/tutorials/typefully-clone.mdx @@ -498,8 +498,8 @@ Now let's add a database to save favorite tweets! We'll use Prisma ORM with Pris ### Install Dependencies ```npm -npm install prisma@7.9.1 tsx --save-dev -npm install @prisma/adapter-pg @prisma/client@7.9.1 dotenv +npm install prisma@7.10.0 tsx --save-dev +npm install @prisma/adapter-pg @prisma/client@7.10.0 dotenv ``` ### Initialize Prisma diff --git a/apps/docs/content/docs/cli/v7/debug.mdx b/apps/docs/content/docs/cli/v7/debug.mdx index a010aeba8b..f0aced50e0 100644 --- a/apps/docs/content/docs/cli/v7/debug.mdx +++ b/apps/docs/content/docs/cli/v7/debug.mdx @@ -100,5 +100,5 @@ false If using an older Prisma version: ```npm -npx prisma@7.9.1 debug +npx prisma@7.10.0 debug ``` diff --git a/apps/docs/content/docs/cli/v7/index.mdx b/apps/docs/content/docs/cli/v7/index.mdx index 82876de69d..eeb134e18b 100644 --- a/apps/docs/content/docs/cli/v7/index.mdx +++ b/apps/docs/content/docs/cli/v7/index.mdx @@ -19,7 +19,7 @@ The Prisma CLI provides commands for: The Prisma CLI is available as an npm package. Install it as a development dependency: ```npm -npm install prisma@7.9.1 --save-dev +npm install prisma@7.10.0 --save-dev ``` :::info diff --git a/apps/docs/content/docs/guides/authentication/authjs/nextjs.mdx b/apps/docs/content/docs/guides/authentication/authjs/nextjs.mdx index 85dde93fa5..0959b8c9e2 100644 --- a/apps/docs/content/docs/guides/authentication/authjs/nextjs.mdx +++ b/apps/docs/content/docs/guides/authentication/authjs/nextjs.mdx @@ -53,11 +53,11 @@ cd authjs-prisma To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/authentication/better-auth/astro.mdx b/apps/docs/content/docs/guides/authentication/better-auth/astro.mdx index 31122a9c54..f3c56535bf 100644 --- a/apps/docs/content/docs/guides/authentication/better-auth/astro.mdx +++ b/apps/docs/content/docs/guides/authentication/better-auth/astro.mdx @@ -51,11 +51,11 @@ Next, you'll add Prisma to your project to manage your database. Install the necessary Prisma packages: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/authentication/better-auth/nextjs.mdx b/apps/docs/content/docs/guides/authentication/better-auth/nextjs.mdx index 83924d8db1..973926bebe 100644 --- a/apps/docs/content/docs/guides/authentication/better-auth/nextjs.mdx +++ b/apps/docs/content/docs/guides/authentication/better-auth/nextjs.mdx @@ -57,11 +57,11 @@ Next, you'll add Prisma to your project to manage your database. Install the necessary Prisma packages. The dependencies differ slightly depending on whether you use Prisma Postgres with Accelerate or another database. ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/authentication/clerk/astro.mdx b/apps/docs/content/docs/guides/authentication/clerk/astro.mdx index d8d18535d1..079c3db251 100644 --- a/apps/docs/content/docs/guides/authentication/clerk/astro.mdx +++ b/apps/docs/content/docs/guides/authentication/clerk/astro.mdx @@ -158,11 +158,11 @@ SignInButton, To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/authentication/clerk/nextjs.mdx b/apps/docs/content/docs/guides/authentication/clerk/nextjs.mdx index bcbbe8688b..78053154d7 100644 --- a/apps/docs/content/docs/guides/authentication/clerk/nextjs.mdx +++ b/apps/docs/content/docs/guides/authentication/clerk/nextjs.mdx @@ -219,11 +219,11 @@ const Navbar = () => { To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/database/data-migration.mdx b/apps/docs/content/docs/guides/database/data-migration.mdx index 2b3cd8d8f3..f6ac0b28b1 100644 --- a/apps/docs/content/docs/guides/database/data-migration.mdx +++ b/apps/docs/content/docs/guides/database/data-migration.mdx @@ -70,11 +70,11 @@ export default defineConfig({ You'll need to install the required packages. If you haven't already, install them using your package manager: ```npm -npm install prisma@7.9.1 @types/pg --save-dev +npm install prisma@7.10.0 @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` If you are using a different database provider (MySQL, SQL Server, SQLite), install the corresponding driver adapter package instead of `@prisma/adapter-pg`. For more information, see [Database drivers](/orm/v7/core-concepts/supported-databases/database-drivers). diff --git a/apps/docs/content/docs/guides/database/multiple-databases.mdx b/apps/docs/content/docs/guides/database/multiple-databases.mdx index 84b9792119..191fade0d3 100644 --- a/apps/docs/content/docs/guides/database/multiple-databases.mdx +++ b/apps/docs/content/docs/guides/database/multiple-databases.mdx @@ -56,11 +56,11 @@ In this section, you will create two separate Prisma Postgres instances—one fo First, install Prisma and the required dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info @@ -76,7 +76,7 @@ You have installed the required dependencies for the project. Initialize Prisma with a [Prisma Postgres](/postgres) instance by running: ```npm -npx prisma@7.9.1 init --db +npx prisma@7.10.0 init --db ``` :::info @@ -87,7 +87,7 @@ If you are not using a Prisma Postgres database, do not use the `--db` flag. Ins Follow the prompts to name your project and choose a database region. -The `prisma@7.9.1 init --db` command: +The `prisma@7.10.0 init --db` command: - Connects your CLI to your [Prisma Data Platform](https://console.prisma.io) account. If you are not logged in or do not have an account, your browser will open to guide you through creating a new account or signing into your existing one. - Creates a `prisma` directory containing a `schema.prisma` file for your database models. diff --git a/apps/docs/content/docs/guides/deployment/bun-workspaces.mdx b/apps/docs/content/docs/guides/deployment/bun-workspaces.mdx index ca48281c13..17ca024d2c 100644 --- a/apps/docs/content/docs/guides/deployment/bun-workspaces.mdx +++ b/apps/docs/content/docs/guides/deployment/bun-workspaces.mdx @@ -58,8 +58,8 @@ npm init Install the required Prisma ORM packages and other dependencies: ```npm -npm install prisma@7.9.1 typescript tsx @types/node @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg +npm install prisma@7.10.0 typescript tsx @types/node @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg ``` :::info diff --git a/apps/docs/content/docs/guides/deployment/cloudflare-d1.mdx b/apps/docs/content/docs/guides/deployment/cloudflare-d1.mdx index c6af87f1f6..1f05b9507e 100644 --- a/apps/docs/content/docs/guides/deployment/cloudflare-d1.mdx +++ b/apps/docs/content/docs/guides/deployment/cloudflare-d1.mdx @@ -37,13 +37,13 @@ cd d1-tutorial And initialize Prisma ORM in the project: ```npm -npx prisma@7.9.1 init --datasource-provider sqlite +npx prisma@7.10.0 init --datasource-provider sqlite ``` And install the Prisma ORM CLI as a development dependency: ```npm -npm install --save-dev prisma@7.9.1 +npm install --save-dev prisma@7.10.0 ``` ## 2. Configure Prisma schema @@ -73,7 +73,7 @@ model User { // [!code ++] Next, install the required packages: ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-d1 dotenv +npm install @prisma/client@7.10.0 @prisma/adapter-d1 dotenv ``` Also, be sure to use a version of the Wrangler CLI that's above [`wrangler@^3.39.0`](https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%403.39.0), otherwise the `--remote` flag that's used in the next sections won't be available. diff --git a/apps/docs/content/docs/guides/deployment/cloudflare-workers.mdx b/apps/docs/content/docs/guides/deployment/cloudflare-workers.mdx index 90c5850762..28febcfc09 100644 --- a/apps/docs/content/docs/guides/deployment/cloudflare-workers.mdx +++ b/apps/docs/content/docs/guides/deployment/cloudflare-workers.mdx @@ -46,11 +46,11 @@ cd prisma-cloudflare-worker To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 dotenv-cli @types/pg --save-dev +npm install prisma@7.10.0 dotenv-cli @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/deployment/docker.mdx b/apps/docs/content/docs/guides/deployment/docker.mdx index 10fb283fde..65feefb517 100644 --- a/apps/docs/content/docs/guides/deployment/docker.mdx +++ b/apps/docs/content/docs/guides/deployment/docker.mdx @@ -66,11 +66,11 @@ This will generate a `package.json` file: Next, install the Prisma CLI as a development dependency and Express.js for the server: ```npm -npm install prisma@7.9.1 @types/pg --save-dev +npm install prisma@7.10.0 @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv express +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv express ``` :::info diff --git a/apps/docs/content/docs/guides/deployment/pnpm-workspaces.mdx b/apps/docs/content/docs/guides/deployment/pnpm-workspaces.mdx index 8fd5954084..afd0dba649 100644 --- a/apps/docs/content/docs/guides/deployment/pnpm-workspaces.mdx +++ b/apps/docs/content/docs/guides/deployment/pnpm-workspaces.mdx @@ -40,12 +40,12 @@ packages: - "packages/*" catalogs: prisma: - prisma: 7.9.1 + prisma: 7.10.0 ``` :::note -The `catalogs` help you pin a certain version of prisma across your repositories. You can learn more about them [here](https://pnpm.io/catalogs). _Explicitly_ pin [prisma](https://www.npmjs.com/package/prisma) to `7.9.1` in the `pnpm-workspace.yaml` file. +The `catalogs` help you pin a certain version of prisma across your repositories. You can learn more about them [here](https://pnpm.io/catalogs). _Explicitly_ pin [prisma](https://www.npmjs.com/package/prisma) to `7.10.0` in the `pnpm-workspace.yaml` file. ::: @@ -107,7 +107,7 @@ pnpm tsc --init Initialize Prisma ORM with an instance of [Prisma Postgres](/postgres) in the `database` package by running the following command: ```bash -pnpm dlx prisma@7.9.1 init +pnpm dlx prisma@7.10.0 init ``` :::info diff --git a/apps/docs/content/docs/guides/deployment/turborepo.mdx b/apps/docs/content/docs/guides/deployment/turborepo.mdx index d90f2c6186..739b3ed291 100644 --- a/apps/docs/content/docs/guides/deployment/turborepo.mdx +++ b/apps/docs/content/docs/guides/deployment/turborepo.mdx @@ -67,8 +67,8 @@ Then initialize it with a `package.json`: Then install the required Prisma ORM dependencies: ```npm -npm install prisma@7.9.1 --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg dotenv +npm install prisma@7.10.0 --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg dotenv ``` :::info @@ -175,10 +175,10 @@ Let's add some scripts to the `package.json` inside `packages/database`: "db:deploy": "prisma migrate deploy" // [!code ++] }, // [!code ++] "devDependencies": { - "prisma": "7.9.1" + "prisma": "7.10.0" }, "dependencies": { - "@prisma/client": "7.9.1", + "@prisma/client": "7.10.0", "@prisma/adapter-pg": "^7.0.0", "pg": "^8.0.0", "dotenv": "^16.0.0" @@ -289,10 +289,10 @@ If you're not using a bundler, use the [Compiled Packages](https://turborepo.dev "db:deploy": "prisma migrate deploy" }, "devDependencies": { - "prisma": "7.9.1" + "prisma": "7.10.0" }, "dependencies": { - "@prisma/client": "7.9.1", + "@prisma/client": "7.10.0", "@prisma/adapter-pg": "^7.0.0", "pg": "^8.0.0", "dotenv": "^16.0.0" diff --git a/apps/docs/content/docs/guides/frameworks/react-router-7.mdx b/apps/docs/content/docs/guides/frameworks/react-router-7.mdx index 1c0dc6fbc4..e7e9a9ea94 100644 --- a/apps/docs/content/docs/guides/frameworks/react-router-7.mdx +++ b/apps/docs/content/docs/guides/frameworks/react-router-7.mdx @@ -46,11 +46,11 @@ cd react-router-7-prisma To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/frameworks/solid-start.mdx b/apps/docs/content/docs/guides/frameworks/solid-start.mdx index 88c6983c28..a18b3edce3 100644 --- a/apps/docs/content/docs/guides/frameworks/solid-start.mdx +++ b/apps/docs/content/docs/guides/frameworks/solid-start.mdx @@ -67,11 +67,11 @@ export default function App() { To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/integrations/ai-sdk.mdx b/apps/docs/content/docs/guides/integrations/ai-sdk.mdx index f38f750f8f..d0d6e71645 100644 --- a/apps/docs/content/docs/guides/integrations/ai-sdk.mdx +++ b/apps/docs/content/docs/guides/integrations/ai-sdk.mdx @@ -53,11 +53,11 @@ cd ai-sdk-prisma To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/integrations/datadog.mdx b/apps/docs/content/docs/guides/integrations/datadog.mdx index 7904bc6330..8ef78c10cf 100644 --- a/apps/docs/content/docs/guides/integrations/datadog.mdx +++ b/apps/docs/content/docs/guides/integrations/datadog.mdx @@ -68,7 +68,7 @@ In this section, you will install Prisma, create your schema, and generate the P Run the following commands to install Prisma and a minimal TypeScript runner: ```npm -npm install -D prisma@7.9.1 tsx +npm install -D prisma@7.10.0 tsx ``` Then initialize Prisma: diff --git a/apps/docs/content/docs/guides/integrations/deno.mdx b/apps/docs/content/docs/guides/integrations/deno.mdx index 44d56f2a37..dd3df845b7 100644 --- a/apps/docs/content/docs/guides/integrations/deno.mdx +++ b/apps/docs/content/docs/guides/integrations/deno.mdx @@ -106,7 +106,7 @@ Update the `dev` task in `deno.json`: Install the Prisma Client, PostgreSQL adapter, and development dependencies: ```npm -deno install npm:@prisma/client@7.9.1 npm:@prisma/adapter-pg npm:pg npm:prisma@7.9.1 npm:@types/pg +deno install npm:@prisma/client@7.10.0 npm:@prisma/adapter-pg npm:pg npm:prisma@7.10.0 npm:@types/pg ``` Initialize Prisma in your project, which creates the necessary configuration files and folder structure for defining your database models. diff --git a/apps/docs/content/docs/guides/integrations/embed-studio.mdx b/apps/docs/content/docs/guides/integrations/embed-studio.mdx index 53f8038f90..dbc8e4b254 100644 --- a/apps/docs/content/docs/guides/integrations/embed-studio.mdx +++ b/apps/docs/content/docs/guides/integrations/embed-studio.mdx @@ -76,22 +76,22 @@ Install the required Prisma packages: ### Prisma Postgres (PostgreSQL) ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev -npm install @prisma/extension-accelerate @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install prisma@7.10.0 tsx @types/pg --save-dev +npm install @prisma/extension-accelerate @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` ### SQLite ```npm -npm install prisma@7.9.1 tsx --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-sqlite dotenv better-sqlite3 +npm install prisma@7.10.0 tsx --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-sqlite dotenv better-sqlite3 ``` ### MySQL ```npm -npm install prisma@7.9.1 tsx @types/mysql2 --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-mysql dotenv mysql2 +npm install prisma@7.10.0 tsx @types/mysql2 --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-mysql dotenv mysql2 ``` :::info diff --git a/apps/docs/content/docs/guides/integrations/github-actions.mdx b/apps/docs/content/docs/guides/integrations/github-actions.mdx index a5d24ba3bb..b51666266f 100644 --- a/apps/docs/content/docs/guides/integrations/github-actions.mdx +++ b/apps/docs/content/docs/guides/integrations/github-actions.mdx @@ -43,11 +43,11 @@ By the end of this section, your project will be fully prepared to use Prisma bo To get started with Prisma, install the required dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg dotenv --save-dev +npm install prisma@7.10.0 tsx @types/pg dotenv --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg ``` :::info diff --git a/apps/docs/content/docs/guides/integrations/neon-accelerate.mdx b/apps/docs/content/docs/guides/integrations/neon-accelerate.mdx index 1e2c2170ae..8d06169b70 100644 --- a/apps/docs/content/docs/guides/integrations/neon-accelerate.mdx +++ b/apps/docs/content/docs/guides/integrations/neon-accelerate.mdx @@ -28,7 +28,7 @@ If you already have a project using Prisma ORM, you can skip the first two steps Start by installing the Prisma CLI in your project: ```npm -npm install prisma@7.9.1 --save-dev +npm install prisma@7.10.0 --save-dev ``` Then, run the following command to initialize a new project: diff --git a/apps/docs/content/docs/guides/integrations/permit-io.mdx b/apps/docs/content/docs/guides/integrations/permit-io.mdx index 8d7e45c355..9034de55ff 100644 --- a/apps/docs/content/docs/guides/integrations/permit-io.mdx +++ b/apps/docs/content/docs/guides/integrations/permit-io.mdx @@ -46,11 +46,11 @@ npm init -y Install application and development dependencies: ```npm -npm install express cors dotenv @prisma/client@7.9.1 @prisma/adapter-pg pg +npm install express cors dotenv @prisma/client@7.10.0 @prisma/adapter-pg pg ``` ```npm -npm install -D prisma@7.9.1 typescript tsx @types/pg +npm install -D prisma@7.10.0 typescript tsx @types/pg ``` :::info diff --git a/apps/docs/content/docs/guides/integrations/shopify.mdx b/apps/docs/content/docs/guides/integrations/shopify.mdx index 6502caab9d..30f0fb9186 100644 --- a/apps/docs/content/docs/guides/integrations/shopify.mdx +++ b/apps/docs/content/docs/guides/integrations/shopify.mdx @@ -135,11 +135,11 @@ model ProductNote { // [!code ++] Next, Prisma will need to be updated to the latest version. Run: ```npm -npm install prisma@7.9.1 @types/pg --save-dev +npm install prisma@7.10.0 @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg ``` :::info diff --git a/apps/docs/content/docs/guides/integrations/supabase-accelerate.mdx b/apps/docs/content/docs/guides/integrations/supabase-accelerate.mdx index 2943dd4e99..da2dcc30af 100644 --- a/apps/docs/content/docs/guides/integrations/supabase-accelerate.mdx +++ b/apps/docs/content/docs/guides/integrations/supabase-accelerate.mdx @@ -30,7 +30,7 @@ If you already have a project using Prisma ORM, you can skip the first two steps Start by installing the Prisma CLI in your project: ```npm -npm install prisma@7.9.1 --save-dev +npm install prisma@7.10.0 --save-dev ``` Then, run the following command to initialize a new project: diff --git a/apps/docs/content/docs/guides/making-guides.mdx b/apps/docs/content/docs/guides/making-guides.mdx index 63e51e7f5a..64c6bf145c 100644 --- a/apps/docs/content/docs/guides/making-guides.mdx +++ b/apps/docs/content/docs/guides/making-guides.mdx @@ -167,7 +167,7 @@ export default defineConfig({ Use ` ```npm ` code blocks for package manager commands. These automatically convert to other package managers (pnpm, yarn, bun) in the UI: ```npm -npm install prisma@7.9.1 --save-dev +npm install prisma@7.10.0 --save-dev ``` ### Environment variables @@ -293,11 +293,11 @@ cd my-app To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/postgres/netlify.mdx b/apps/docs/content/docs/guides/postgres/netlify.mdx index baaf42b903..f2095e0a09 100644 --- a/apps/docs/content/docs/guides/postgres/netlify.mdx +++ b/apps/docs/content/docs/guides/postgres/netlify.mdx @@ -117,7 +117,7 @@ In this section, you are going to add Prisma Postgres to the starter project _on 1. Install the Prisma CLI as a development dependency: ```npm -npm install prisma@7.9.1 --save-dev +npm install prisma@7.10.0 --save-dev ``` 4. Initialize Prisma ORM to create Prisma schema, config and `.env` file: @@ -229,7 +229,7 @@ As mentioned [above](#generate-prisma-client-in-a-postinstall-script-in-packagej }, "dependencies": { "@netlify/blobs": "^8.1.0", - "@prisma/client": "7.9.1", + "@prisma/client": "7.10.0", "@prisma/extension-accelerate": "^1.2.1", "blobshape": "^1.0.0", "bright": "^0.8.5", @@ -245,7 +245,7 @@ As mentioned [above](#generate-prisma-client-in-a-postinstall-script-in-packagej "eslint": "8.57.1", "eslint-config-next": "15.1.6", "postcss": "^8.4.36", - "prisma": "7.9.1", + "prisma": "7.10.0", "tailwindcss": "^3.4.1" } } diff --git a/apps/docs/content/docs/guides/switch-to-prisma-orm/from-drizzle.mdx b/apps/docs/content/docs/guides/switch-to-prisma-orm/from-drizzle.mdx index b3bd214426..a7caf3a0e3 100644 --- a/apps/docs/content/docs/guides/switch-to-prisma-orm/from-drizzle.mdx +++ b/apps/docs/content/docs/guides/switch-to-prisma-orm/from-drizzle.mdx @@ -49,8 +49,8 @@ Prisma ORM lends itself really well for **incremental adoption**. This means, yo The first step to adopt Prisma ORM is to [install the Prisma CLI](/orm/v7/reference/prisma-cli-reference) in your project: ```npm -npm install prisma@7.9.1 @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg +npm install prisma@7.10.0 @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg ``` :::info diff --git a/apps/docs/content/docs/guides/switch-to-prisma-orm/from-sql-orms.mdx b/apps/docs/content/docs/guides/switch-to-prisma-orm/from-sql-orms.mdx index 64477cadc8..0a80e11c8c 100644 --- a/apps/docs/content/docs/guides/switch-to-prisma-orm/from-sql-orms.mdx +++ b/apps/docs/content/docs/guides/switch-to-prisma-orm/from-sql-orms.mdx @@ -37,8 +37,8 @@ Prisma ORM supports **incremental adoption**, so you can migrate your project st ## Step 1. Install the Prisma CLI ```npm -npm install prisma@7.9.1 --save-dev -npm install @prisma/client@7.9.1 +npm install prisma@7.10.0 --save-dev +npm install @prisma/client@7.10.0 ``` ## Step 2. Introspect your database diff --git a/apps/docs/content/docs/guides/upgrade-prisma-orm/postgresql.mdx b/apps/docs/content/docs/guides/upgrade-prisma-orm/postgresql.mdx index 0b5bae2d4e..01d664e69f 100644 --- a/apps/docs/content/docs/guides/upgrade-prisma-orm/postgresql.mdx +++ b/apps/docs/content/docs/guides/upgrade-prisma-orm/postgresql.mdx @@ -53,11 +53,11 @@ The guide follows a small Hono API with two routes. Map the file names to your o "db:migrate": "prisma migrate dev" }, "dependencies": { - "@prisma/adapter-pg": "^7.9.1", - "@prisma/client": "^7.9.1" + "@prisma/adapter-pg": "^7.10.0", + "@prisma/client": "^7.10.0" }, "devDependencies": { - "prisma": "^7.9.1" + "prisma": "^7.10.0" } } ``` diff --git a/apps/docs/content/docs/guides/upgrade-prisma-orm/v1.mdx b/apps/docs/content/docs/guides/upgrade-prisma-orm/v1.mdx index 3c3c0a0670..105a44b74a 100644 --- a/apps/docs/content/docs/guides/upgrade-prisma-orm/v1.mdx +++ b/apps/docs/content/docs/guides/upgrade-prisma-orm/v1.mdx @@ -44,7 +44,7 @@ This guide provides a comprehensive roadmap for migrating your project from Pris ```npm # Initialize a new project npm init -y -npm install prisma@7.9.1 @prisma/client@7.9.1 +npm install prisma@7.10.0 @prisma/client@7.10.0 # Initialize Prisma npx prisma init diff --git a/apps/docs/content/docs/guides/v7/frameworks/astro.mdx b/apps/docs/content/docs/guides/v7/frameworks/astro.mdx index dac2cb2e15..afa40b147c 100644 --- a/apps/docs/content/docs/guides/v7/frameworks/astro.mdx +++ b/apps/docs/content/docs/guides/v7/frameworks/astro.mdx @@ -58,11 +58,11 @@ cd astro-prisma To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/v7/frameworks/elysia.mdx b/apps/docs/content/docs/guides/v7/frameworks/elysia.mdx index 1acc3c8b37..89b67b3f34 100644 --- a/apps/docs/content/docs/guides/v7/frameworks/elysia.mdx +++ b/apps/docs/content/docs/guides/v7/frameworks/elysia.mdx @@ -48,8 +48,8 @@ cd elysia-prisma Install the required Prisma packages, database adapter, and Prismabox (for generated TypeBox schemas): ```npm -npm install prisma@7.9.1 bun-types --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg prismabox +npm install prisma@7.10.0 bun-types --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg prismabox ``` :::info diff --git a/apps/docs/content/docs/guides/v7/frameworks/hono.mdx b/apps/docs/content/docs/guides/v7/frameworks/hono.mdx index 086bd22a4e..b0480c130b 100644 --- a/apps/docs/content/docs/guides/v7/frameworks/hono.mdx +++ b/apps/docs/content/docs/guides/v7/frameworks/hono.mdx @@ -50,11 +50,11 @@ npm create hono@latest To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/v7/frameworks/nestjs.mdx b/apps/docs/content/docs/guides/v7/frameworks/nestjs.mdx index 890d2dc96b..67fc7b3764 100644 --- a/apps/docs/content/docs/guides/v7/frameworks/nestjs.mdx +++ b/apps/docs/content/docs/guides/v7/frameworks/nestjs.mdx @@ -66,11 +66,11 @@ In `package.json`, add the `type` field set to `"module"`: Install the necessary Prisma packages and database drivers: ```npm -npm install prisma@7.9.1 --save-dev +npm install prisma@7.10.0 --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg ``` :::info diff --git a/apps/docs/content/docs/guides/v7/frameworks/nextjs.mdx b/apps/docs/content/docs/guides/v7/frameworks/nextjs.mdx index e132ef3fb5..ba81dc7d32 100644 --- a/apps/docs/content/docs/guides/v7/frameworks/nextjs.mdx +++ b/apps/docs/content/docs/guides/v7/frameworks/nextjs.mdx @@ -66,11 +66,11 @@ cd nextjs-prisma To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/v7/frameworks/nuxt.mdx b/apps/docs/content/docs/guides/v7/frameworks/nuxt.mdx index 7f2f99a227..dc3c73276a 100644 --- a/apps/docs/content/docs/guides/v7/frameworks/nuxt.mdx +++ b/apps/docs/content/docs/guides/v7/frameworks/nuxt.mdx @@ -40,11 +40,11 @@ cd hello-prisma ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg ``` ```npm -npm install -D prisma@7.9.1 @types/pg dotenv tsx +npm install -D prisma@7.10.0 @types/pg dotenv tsx ``` ## 2. Initialize Prisma diff --git a/apps/docs/content/docs/guides/v7/frameworks/sveltekit.mdx b/apps/docs/content/docs/guides/v7/frameworks/sveltekit.mdx index 83f60c8f69..16f16c2350 100644 --- a/apps/docs/content/docs/guides/v7/frameworks/sveltekit.mdx +++ b/apps/docs/content/docs/guides/v7/frameworks/sveltekit.mdx @@ -67,11 +67,11 @@ That's it! Svelte makes it a very simple process to get up and running. At this To get started with Prisma, you'll need to install a few dependencies: ```npm -npm install prisma@7.9.1 tsx @types/pg --save-dev +npm install prisma@7.10.0 tsx @types/pg --save-dev ``` ```npm -npm install @prisma/client@7.9.1 @prisma/adapter-pg dotenv pg +npm install @prisma/client@7.10.0 @prisma/adapter-pg dotenv pg ``` :::info diff --git a/apps/docs/content/docs/guides/v7/runtimes/bun.mdx b/apps/docs/content/docs/guides/v7/runtimes/bun.mdx index 6c894e5b24..2c137127fe 100644 --- a/apps/docs/content/docs/guides/v7/runtimes/bun.mdx +++ b/apps/docs/content/docs/guides/v7/runtimes/bun.mdx @@ -43,8 +43,8 @@ This creates a basic Bun project that includes a `package.json` file and an `ind Install the required Prisma packages and other dependencies: ```npm -npm install prisma@7.9.1 @types/pg --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg +npm install prisma@7.10.0 @types/pg --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg ``` :::info diff --git a/apps/docs/content/docs/guides/v7/runtimes/deno.mdx b/apps/docs/content/docs/guides/v7/runtimes/deno.mdx index 2e4436423e..aea0449776 100644 --- a/apps/docs/content/docs/guides/v7/runtimes/deno.mdx +++ b/apps/docs/content/docs/guides/v7/runtimes/deno.mdx @@ -49,8 +49,8 @@ Update the `deno.json` file with the following configuration to set up Node.js c }, "imports": { "@prisma/adapter-pg": "npm:@prisma/adapter-pg@^7.0.0", - "@prisma/client": "npm:@prisma/client@7.9.1", - "prisma": "npm:prisma@7.9.1" + "@prisma/client": "npm:@prisma/client@7.10.0", + "prisma": "npm:prisma@7.10.0" }, "tasks": { "dev": "deno run -A --env=.env --watch main.ts", @@ -75,7 +75,7 @@ The `nodeModulesDir: "auto"` setting allows Deno to automatically manage a `node Initialize Prisma ORM with Prisma Postgres in your project: ```bash -deno run -A npm:prisma@7.9.1 init +deno run -A npm:prisma@7.10.0 init ``` :::info diff --git a/apps/docs/content/docs/orm/v7/index.mdx b/apps/docs/content/docs/orm/v7/index.mdx index b08bb01346..77243f8671 100644 --- a/apps/docs/content/docs/orm/v7/index.mdx +++ b/apps/docs/content/docs/orm/v7/index.mdx @@ -43,7 +43,7 @@ Add Prisma ORM 7 to this project with my existing database. If I have not given you a database connection string and none exists in the project, stop and ask. -1. Run `npx prisma@7.9.1 init` (Prisma 7). For an existing database, set DATABASE_URL in `.env` and introspect it with `npx prisma db pull`; for a new schema, define models in `prisma/schema.prisma` and run `npx prisma migrate dev --name init`. If migrate dev asks to reset the database, stop and ask me first. +1. Run `npx prisma@7.10.0 init` (Prisma 7). For an existing database, set DATABASE_URL in `.env` and introspect it with `npx prisma db pull`; for a new schema, define models in `prisma/schema.prisma` and run `npx prisma migrate dev --name init`. If migrate dev asks to reset the database, stop and ask me first. 2. Install the driver adapter for the database (Prisma 7 requires one), e.g. `npm install @prisma/adapter-pg` for PostgreSQL, and pass it to `new PrismaClient({ adapter })`. Generate the client with `npx prisma generate` and write one query in an existing code path. 3. Run the query (e.g. with `npx tsx`) and show me the output, the schema, and the query you added. @@ -147,7 +147,7 @@ npx prisma db pull Generate and use the type-safe client: ```npm -npm install @prisma/client@7.9.1 +npm install @prisma/client@7.10.0 npx prisma generate ``` diff --git a/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/shared-extensions/permit-rbac.mdx b/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/shared-extensions/permit-rbac.mdx index 7bd9ce3a70..e4a46b9478 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/shared-extensions/permit-rbac.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/client-extensions/shared-extensions/permit-rbac.mdx @@ -74,7 +74,7 @@ Before implementing fine-grained authorization with Prisma, make sure you have: Install the extension alongside Prisma Client: ```npm -npm install @permitio/permit-prisma @prisma/client@7.9.1 +npm install @permitio/permit-prisma @prisma/client@7.10.0 ``` You'll also need to sign up for a [Permit account](https://app.permit.io) to define your authorization policies. diff --git a/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-cloudflare.mdx b/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-cloudflare.mdx index 96f922c61b..c428fd7bb3 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-cloudflare.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-cloudflare.mdx @@ -30,7 +30,7 @@ You can use Prisma Postgres and deploy to Cloudflare Workers. After you create a Worker, run: ```npm -npx prisma@7.9.1 init --db +npx prisma@7.10.0 init --db ``` Enter a name for your project and choose a database region. @@ -164,7 +164,7 @@ If you don't have that yet, you can run these commands: ```npm npm create cloudflare@latest prisma-cloudflare-worker-example -- --type hello-world cd prisma-cloudflare-worker-example -npm install prisma@7.9.1 --save-dev && npm install @prisma/client@7.9.1 +npm install prisma@7.10.0 --save-dev && npm install @prisma/client@7.10.0 npx prisma init --output ../generated/prisma ``` diff --git a/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx b/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx index 305f9dda7b..ad80bb1ec2 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx @@ -23,7 +23,7 @@ Create a new directory and initialize your Prisma project: ```npm mkdir prisma-deno-deploy cd prisma-deno-deploy -deno run -A npm:prisma@7.9.1 init --db +deno run -A npm:prisma@7.10.0 init --db ``` Enter a name for your project and choose a database region. @@ -47,8 +47,8 @@ Create a `deno.json` file with the following configuration: }, "imports": { "@prisma/adapter-pg": "npm:@prisma/adapter-pg@^7.0.0", - "@prisma/client": "npm:@prisma/client@7.9.1", - "prisma": "npm:prisma@7.9.1" + "@prisma/client": "npm:@prisma/client@7.10.0", + "prisma": "npm:prisma@7.10.0" }, "tasks": { "dev": "deno run -A --env=.env --watch index.ts", diff --git a/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-vercel.mdx b/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-vercel.mdx index 805f923857..94516b5930 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-vercel.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/deployment/edge/deploy-to-vercel.mdx @@ -131,7 +131,7 @@ npx create-next-app@latest ``` ```npm -npm install prisma@7.9.1 --save-dev && npm install @prisma/client@7.9.1 +npm install prisma@7.10.0 --save-dev && npm install @prisma/client@7.10.0 ``` ```npm diff --git a/apps/docs/content/docs/orm/v7/prisma-client/index.mdx b/apps/docs/content/docs/orm/v7/prisma-client/index.mdx index c9e4cfdc73..4ac035f13f 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/index.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/index.mdx @@ -29,7 +29,7 @@ generator client { ### 2. Install Prisma Client ```npm -npm install @prisma/client@7.9.1 +npm install @prisma/client@7.10.0 ``` ### 3. Generate the client diff --git a/apps/docs/content/docs/orm/v7/prisma-client/observability-and-logging/opentelemetry-tracing.mdx b/apps/docs/content/docs/orm/v7/prisma-client/observability-and-logging/opentelemetry-tracing.mdx index 687f2849f9..cb2441a9e0 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/observability-and-logging/opentelemetry-tracing.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/observability-and-logging/opentelemetry-tracing.mdx @@ -89,8 +89,8 @@ This section explains how to install and register tracing in your application. Install the `prisma`, `@prisma/client`, and `@prisma/instrumentation` npm packages. You will also need to install the `@opentelemetry/api` package as it's a peer dependency. ```npm -npm install prisma@7.9.1 --save-dev -npm install @prisma/client@7.9.1 --save +npm install prisma@7.10.0 --save-dev +npm install @prisma/client@7.10.0 --save npm install @prisma/instrumentation@latest --save npm install @opentelemetry/api@latest --save ``` diff --git a/apps/docs/content/docs/orm/v7/prisma-client/setup-and-configuration/introduction.mdx b/apps/docs/content/docs/orm/v7/prisma-client/setup-and-configuration/introduction.mdx index bd66853fc6..835d67c9a2 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/setup-and-configuration/introduction.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/setup-and-configuration/introduction.mdx @@ -49,18 +49,18 @@ model User { [Install the Prisma CLI](/orm/v7/reference/prisma-cli-reference), the Prisma Client library, and the [driver adapter](/orm/v7/core-concepts/supported-databases/database-drivers) for your database: ```npm tab="PostgreSQL" -npm install prisma@7.9.1 --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-pg pg +npm install prisma@7.10.0 --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-pg pg ``` ```npm tab="MySQL / MariaDB" -npm install prisma@7.9.1 --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-mariadb mariadb +npm install prisma@7.10.0 --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-mariadb mariadb ``` ```npm tab="SQLite" -npm install prisma@7.9.1 --save-dev -npm install @prisma/client@7.9.1 @prisma/adapter-better-sqlite3 better-sqlite3 +npm install prisma@7.10.0 --save-dev +npm install @prisma/client@7.10.0 @prisma/adapter-better-sqlite3 better-sqlite3 ``` :::note diff --git a/apps/docs/content/docs/orm/v7/prisma-client/using-raw-sql/typedsql.mdx b/apps/docs/content/docs/orm/v7/prisma-client/using-raw-sql/typedsql.mdx index ce65fb9b57..69687e864b 100644 --- a/apps/docs/content/docs/orm/v7/prisma-client/using-raw-sql/typedsql.mdx +++ b/apps/docs/content/docs/orm/v7/prisma-client/using-raw-sql/typedsql.mdx @@ -14,8 +14,8 @@ To start using TypedSQL in your Prisma project, follow these steps: 1. Ensure you have `@prisma/client` and `prisma` installed: ```npm - npm install @prisma/client@7.9.1 - npm install -D prisma@7.9.1 + npm install @prisma/client@7.10.0 + npm install -D prisma@7.10.0 ``` 1. Add the `typedSql` preview feature flag to your `schema.prisma` file: diff --git a/apps/docs/content/docs/orm/v7/reference/prisma-cli-reference.mdx b/apps/docs/content/docs/orm/v7/reference/prisma-cli-reference.mdx index 1a18a80fde..935c08b307 100644 --- a/apps/docs/content/docs/orm/v7/reference/prisma-cli-reference.mdx +++ b/apps/docs/content/docs/orm/v7/reference/prisma-cli-reference.mdx @@ -672,7 +672,7 @@ false If you're using an older version of Prisma, you can use this command by running: ```npm -npx prisma@7.9.1 debug +npx prisma@7.10.0 debug ``` ## `dev` diff --git a/apps/docs/content/docs/postgres/troubleshooting.mdx b/apps/docs/content/docs/postgres/troubleshooting.mdx index ffcf9772f8..fa3a75e8fc 100644 --- a/apps/docs/content/docs/postgres/troubleshooting.mdx +++ b/apps/docs/content/docs/postgres/troubleshooting.mdx @@ -27,7 +27,7 @@ This can occur due to npx caching. If you've previously run `npx prisma init`, y Explicitly run a pinned Prisma 7 CLI version: ```npm -npx prisma@7.9.1 init --db +npx prisma@7.10.0 init --db ``` This ensures that you're using a Prisma 7 CLI that supports the flag, preventing issues with outdated command syntax. @@ -39,7 +39,7 @@ This ensures that you're using a Prisma 7 CLI that supports the flag, preventing When running the command: ```npm -npx prisma@7.9.1 init --db +npx prisma@7.10.0 init --db ``` You may encounter the following error message in your logs: diff --git a/apps/docs/content/docs/studio/getting-started.mdx b/apps/docs/content/docs/studio/getting-started.mdx index 3bb8763614..91958394ab 100644 --- a/apps/docs/content/docs/studio/getting-started.mdx +++ b/apps/docs/content/docs/studio/getting-started.mdx @@ -11,7 +11,7 @@ metaDescription: 'Learn how to install Prisma Studio, connect to your database, Prisma Studio comes bundled with the Prisma CLI. To get started, make sure you have Node.js installed, then install the Prisma CLI: ```npm -npm install -g prisma@7.9.1 +npm install -g prisma@7.10.0 ``` ## Launching Studio diff --git a/apps/docs/content/docs/studio/prisma-next.mdx b/apps/docs/content/docs/studio/prisma-next.mdx index e204671c60..c8b00b6867 100644 --- a/apps/docs/content/docs/studio/prisma-next.mdx +++ b/apps/docs/content/docs/studio/prisma-next.mdx @@ -10,7 +10,7 @@ Prisma Studio shows the migration history of your [Prisma 8](/orm) database as a This guide takes you from an empty directory to inspecting your own migration history. For browsing, editing, and filtering data in general, see [Getting Started](/studio/getting-started). -The Migrations view requires `@prisma/studio-core` 0.32.0 or later, which ships in the stable Prisma CLI since 7.9. Run Studio with `npx prisma@7.9.1 studio`. See the [Prisma 8 docs](/orm). +The Migrations view requires `@prisma/studio-core` 0.32.0 or later, which ships in the stable Prisma CLI since 7.9. Run Studio with `npx prisma@7.10.0 studio`. See the [Prisma 8 docs](/orm). ## Prerequisites @@ -127,7 +127,7 @@ Open the URL the command prints; the seeded users come back through the Prisma 8 A Prisma 8 project has no `schema.prisma`, so pass the [connection string](/postgres/database/connecting-to-your-database) with `--url`. Run Studio from a directory outside the project: the Prisma 7 CLI that ships Studio cannot read the Prisma 8 `prisma.config.ts` and fails if it finds one: ```bash -cd .. && npx prisma@7.9.1 studio --url "$DATABASE_URL" +cd .. && npx prisma@7.10.0 studio --url "$DATABASE_URL" ``` Studio prints the local URL it serves on. Once the database has at least one applied migration, a **Migrations** item appears in the left navigation. @@ -200,13 +200,13 @@ The hashes are the same ones that make Prisma 8 migrations [a graph rather than | Surface | Available | |---|---| -| Local Studio (`npx prisma@7.9.1 studio`) | Yes, with `@prisma/studio-core` 0.32.0 or later | +| Local Studio (`npx prisma@7.10.0 studio`) | Yes, with `@prisma/studio-core` 0.32.0 or later | | [Prisma Console](https://console.prisma.io) (embedded Studio) | Yes, for databases with an applied Prisma 8 migration history | | Prisma ORM projects using `prisma migrate` | No | In Prisma Console, open your database's Studio tab and select **Migrations**. The view is the same as local Studio, the selected migration is part of the Console URL, and no local setup is required. -The stable Prisma CLI bundles the Migrations view since 7.9 (`@prisma/studio-core` 0.33.0). Run `npx prisma@7.9.1 studio` from a directory outside your Prisma 8 project; the Prisma 7 CLI cannot read the Prisma 8 `prisma.config.ts`. +The stable Prisma CLI bundles the Migrations view since 7.9 (`@prisma/studio-core` 0.33.0). Run `npx prisma@7.10.0 studio` from a directory outside your Prisma 8 project; the Prisma 7 CLI cannot read the Prisma 8 `prisma.config.ts`. ## Limitations diff --git a/apps/docs/src/app/(docs)/(default)/layout.tsx b/apps/docs/src/app/(docs)/(default)/layout.tsx index 5729946db4..f342882466 100644 --- a/apps/docs/src/app/(docs)/(default)/layout.tsx +++ b/apps/docs/src/app/(docs)/(default)/layout.tsx @@ -5,7 +5,6 @@ import type { LinkItemType } from "@/components/layout/link-item"; import { DocsLayout } from "@/components/layout/notebook"; import { StatusIndicator } from "@/components/status-indicator"; import { SidebarBannerCarousel, type BannerSlide } from "@/components/sidebar-banner"; -import { fetchOgImage } from "@/lib/og-image"; import { cn } from "@prisma-docs/ui/lib/cn"; import { getPageBadges } from "@/lib/page-badges"; import { BadgeProvider, SidebarBadgeItem } from "@/components/sidebar-badge-provider"; @@ -21,9 +20,7 @@ const SIDEBAR_SLIDES: BannerSlide[] = [ href: "https://pris.ly/pn-anouncement", gradient: "orm" as const, badge: "New", - // Brand-drawn tile (see sidebar-banner.tsx) — the previous raster was - // old-brand navy/indigo artwork, the last off-palette element in the shell. - visual: "prism" as const, + cta: "Read the post", }, ]; @@ -32,17 +29,6 @@ export default async function Layout({ children }: { children: React.ReactNode } const navbarLinks: LinkItemType[] = [...links, ...authLinks]; - // Resolve OG images server-side for slides that don't have a hardcoded image - const slides = await Promise.all( - SIDEBAR_SLIDES.map(async (slide) => { - if (!slide.image && !slide.visual && slide.href.startsWith("http")) { - const ogImage = await fetchOgImage(slide.href); - if (ogImage) return { ...slide, image: ogImage }; - } - return slide; - }), - ); - const badges = Object.fromEntries(getPageBadges()); const ormVersions = getOrmVersions(source.pageTree); const pageUrls = source.getPages().map((page) => page.url); @@ -59,7 +45,7 @@ export default async function Layout({ children }: { children: React.ReactNode } components: { Item: SidebarBadgeItem }, footer: ({ className, ...props }: ComponentProps<"div">) => (
- +
), diff --git a/apps/docs/src/app/global.css b/apps/docs/src/app/global.css index 53ac869e56..75c32328d0 100644 --- a/apps/docs/src/app/global.css +++ b/apps/docs/src/app/global.css @@ -184,28 +184,62 @@ header &[data-search-full] { } /* --------------------------------------------------------------------------- - Prisma Next banner — the one loud brand moment in an otherwise quiet shell. - - Structure is unchanged (flow / sweep / grid keyframes, reduced-motion - guard); only the palette moved. The old teal becomes prism cyan-500 - (`0 187 203` where an rgba() is needed, since custom properties cannot be - spliced into an rgba channel list), the old indigo-blue is dropped - entirely rather than re-hued, and the navy base ramp is rebuilt as ink with - faint prism tints. The result reads spectrum, not rainbow: cyan dominates - the resting surface, and yellow / orange / pink appear only as the sweep's - passing highlights. + Prisma 8 banner — the one loud brand moment in an otherwise quiet shell. + + Two surfaces, one structure. Light mode is paper with a cyan-to-yellow + wash and an ink CTA; dark mode is ink with the same prism tints and a + cyan-ringed CTA. Both carry the full-width spectrum hairline along the + bottom edge (the brand's interaction signature), a travelling spectrum + highlight, and a faint diagonal grid. Selectors hang off the class, not the + Banner id, so renaming the dismissal key does not silently drop the style. --------------------------------------------------------------------------- */ -#prisma-next-docs.prisma-next-banner { +.prisma-next-banner { isolation: isolate; overflow: hidden; + color: var(--color-foreground-neutral); + border-bottom: 1px solid color-mix(in oklab, var(--color-prism-cyan-400) 45%, #ffffff); + background: + linear-gradient(100deg, rgba(1, 215, 228, 0.22), transparent 30%), + linear-gradient(260deg, rgba(243, 195, 6, 0.18), transparent 32%), + linear-gradient( + 90deg, + #ffffff 0%, + color-mix(in srgb, var(--color-prism-cyan-50) 70%, #ffffff) 36%, + color-mix(in srgb, var(--color-prism-yellow-50) 60%, #ffffff) 68%, + #ffffff 100% + ), + repeating-linear-gradient( + 115deg, + rgba(15, 15, 15, 0.05) 0, + rgba(15, 15, 15, 0.05) 1px, + transparent 1px, + transparent 18px + ); + background-position: + 0% 50%, + 100% 50%, + 0% 50%, + 0 0; + background-size: + 150% 100%, + 150% 100%, + 220% 100%, + 48px 48px; + box-shadow: + 0 8px 28px rgba(1, 215, 228, 0.12), + inset 0 -1px 0 rgba(15, 15, 15, 0.06); + animation: prisma-next-banner-flow 16s ease-in-out infinite alternate; +} + +.dark .prisma-next-banner { color: #fafafa; - border-bottom: 1px solid - color-mix(in oklab, var(--color-prism-cyan-500) 55%, var(--color-prism-cyan-900)); + border-bottom-color: color-mix( + in oklab, + var(--color-prism-cyan-500) 55%, + var(--color-prism-cyan-900) + ); background: linear-gradient(100deg, rgba(0, 187, 203, 0.32), transparent 28%), - /* prism yellow-300 is markedly more saturated than the amber it replaces, - so its wash is dialled back from 0.28 to keep the surface cyan-dominant - rather than tipping olive on the right-hand third. */ linear-gradient(260deg, rgba(243, 195, 6, 0.2), transparent 30%), linear-gradient( 90deg, @@ -235,11 +269,10 @@ header &[data-search-full] { 0 8px 32px rgba(0, 187, 203, 0.16), inset 0 1px 0 rgba(255, 255, 255, 0.12), inset 0 -1px 0 rgba(0, 0, 0, 0.32); - animation: prisma-next-banner-flow 16s ease-in-out infinite alternate; } -#prisma-next-docs.prisma-next-banner::before, -#prisma-next-docs.prisma-next-banner::after { +.prisma-next-banner::before, +.prisma-next-banner::after { content: ""; position: absolute; inset: 0; @@ -247,25 +280,23 @@ header &[data-search-full] { } /* Layer 1 is the travelling highlight — four spectrum stops in gradient order - (cyan → yellow → orange → pink) replacing the old teal/indigo/amber/rose - run. Layer 2 is the 2px rule along the bottom edge, and it takes - `--gradient-spectrum` verbatim: a full-width spectrum hairline is exactly - the brand's interaction signature. */ -#prisma-next-docs.prisma-next-banner::before { + (cyan → yellow → orange → pink). Layer 2 is the 2px rule along the bottom + edge, and it takes `--gradient-spectrum` verbatim. */ +.prisma-next-banner::before { background: linear-gradient( 90deg, transparent 0%, - rgba(1, 215, 228, 0.28) 18%, - rgba(243, 195, 6, 0.44) 38%, - rgba(243, 122, 3, 0.4) 56%, - rgba(240, 14, 92, 0.28) 74%, + rgba(1, 215, 228, 0.22) 18%, + rgba(243, 195, 6, 0.3) 38%, + rgba(243, 122, 3, 0.26) 56%, + rgba(240, 14, 92, 0.18) 74%, transparent 100% ), var(--gradient-spectrum); background-position: -42rem 0, - 0 0; + 0 100%; background-repeat: no-repeat; background-size: 42rem 100%, @@ -273,16 +304,30 @@ header &[data-search-full] { animation: prisma-next-banner-sweep 8s ease-in-out infinite; } -#prisma-next-docs.prisma-next-banner::after { - opacity: 0.48; +.dark .prisma-next-banner::before { + background-image: + linear-gradient( + 90deg, + transparent 0%, + rgba(1, 215, 228, 0.28) 18%, + rgba(243, 195, 6, 0.44) 38%, + rgba(243, 122, 3, 0.4) 56%, + rgba(240, 14, 92, 0.28) 74%, + transparent 100% + ), + var(--gradient-spectrum); +} + +.prisma-next-banner::after { + opacity: 0.35; background: - linear-gradient(90deg, transparent, rgba(255, 255, 255, 0.18), transparent), + linear-gradient(90deg, transparent, rgba(255, 255, 255, 0.5), transparent), repeating-linear-gradient( 135deg, transparent 0, transparent 16px, - rgba(255, 255, 255, 0.16) 16px, - rgba(255, 255, 255, 0.16) 17px + rgba(15, 15, 15, 0.06) 16px, + rgba(15, 15, 15, 0.06) 17px ); background-position: -30% 0, @@ -290,11 +335,24 @@ header &[data-search-full] { background-size: 24rem 100%, 32px 32px; - mix-blend-mode: screen; animation: prisma-next-banner-grid 20s linear infinite; } -#prisma-next-docs .prisma-next-banner-content { +.dark .prisma-next-banner::after { + opacity: 0.48; + background-image: + linear-gradient(90deg, transparent, rgba(255, 255, 255, 0.18), transparent), + repeating-linear-gradient( + 135deg, + transparent 0, + transparent 16px, + rgba(255, 255, 255, 0.16) 16px, + rgba(255, 255, 255, 0.16) 17px + ); + mix-blend-mode: screen; +} + +.prisma-next-banner .prisma-next-banner-content { position: relative; z-index: 1; } @@ -303,26 +361,38 @@ header &[data-search-full] { over fumadocs' absolutely-positioned close button (z-index auto) and swallows its clicks. Lift the button above the strip so the cross stays clickable. */ -#prisma-next-docs.prisma-next-banner > button { +.prisma-next-banner > button { z-index: 2; } -/* The banner surface is dark in either theme, so its secondary copy cannot - ride `--fd-muted-foreground` — in light mode that resolves to #646567 and - all but disappears against the ink. It takes the dark ramp's weak neutral - directly instead. */ -#prisma-next-docs .prisma-next-banner-content .text-fd-muted-foreground { +.prisma-next-banner .prisma-next-banner-content .text-fd-muted-foreground { + color: var(--color-foreground-neutral-weak); +} + +.dark .prisma-next-banner .prisma-next-banner-content .text-fd-muted-foreground { color: #a5a5a6; } -/* The CTA sits on the same always-dark surface as the banner, so it is built - from the same ink + prism-tint logic rather than the mode-aware tokens. */ -#prisma-next-docs .prisma-next-banner-cta { +/* The CTA inverts the surface: ink on paper, and in dark mode a cyan-ringed + ink pill lifted by a prism glow. */ +.prisma-next-banner .prisma-next-banner-cta { display: inline-flex; align-items: center; gap: 4px; - border-color: color-mix(in oklab, var(--color-prism-cyan-500) 48%, #ffffff); + border-color: #151515; color: #fafafa; + background: #151515; + box-shadow: 0 4px 16px rgba(1, 215, 228, 0.22); +} + +.prisma-next-banner .prisma-next-banner-cta:hover { + color: #ffffff; + background: #2a2a2a; + border-color: #2a2a2a; +} + +.dark .prisma-next-banner .prisma-next-banner-cta { + border-color: color-mix(in oklab, var(--color-prism-cyan-500) 48%, #ffffff); background: linear-gradient( 135deg, color-mix(in srgb, var(--color-prism-cyan-950) 55%, #0f0f0f), @@ -334,8 +404,8 @@ header &[data-search-full] { inset 0 1px 0 rgba(255, 255, 255, 0.18); } -#prisma-next-docs .prisma-next-banner-cta:hover { - color: #ffffff; +.dark .prisma-next-banner .prisma-next-banner-cta:hover { + border-color: color-mix(in oklab, var(--color-prism-cyan-400) 70%, #ffffff); background: linear-gradient( 135deg, color-mix(in srgb, var(--color-prism-cyan-900) 65%, #0f0f0f), @@ -367,14 +437,14 @@ header &[data-search-full] { 24% { background-position: -42rem 0, - 0 0; + 0 100%; } 68%, 100% { background-position: calc(100% + 42rem) 0, - 0 0; + 0 100%; } } @@ -387,9 +457,9 @@ header &[data-search-full] { } @media (prefers-reduced-motion: reduce) { - #prisma-next-docs.prisma-next-banner, - #prisma-next-docs.prisma-next-banner::before, - #prisma-next-docs.prisma-next-banner::after { + .prisma-next-banner, + .prisma-next-banner::before, + .prisma-next-banner::after { animation: none; } } diff --git a/apps/docs/src/components/sidebar-banner.tsx b/apps/docs/src/components/sidebar-banner.tsx index 355f9b8d62..47d602576d 100644 --- a/apps/docs/src/components/sidebar-banner.tsx +++ b/apps/docs/src/components/sidebar-banner.tsx @@ -9,12 +9,11 @@ export interface BannerSlide { title: string; description: string; href: string; + /** Accent for the badge and link: ORM amber or platform cyan. */ gradient?: "orm" | "ppg"; badge?: string; - image?: string; - imageAlt?: string; - /** Brand-drawn tile instead of a raster — stays on-palette by construction. */ - visual?: "prism"; + /** Link label; defaults to "Read more". */ + cta?: string; } interface SidebarBannerCarouselProps { @@ -65,6 +64,7 @@ export function SidebarBannerCarousel({ slides }: SidebarBannerCarouselProps) { } const front = visibleSlides[0]; + const isPpg = front.gradient === "ppg"; // Peek cards rendered furthest-back first so DOM order = visual stacking const peekCards = visibleSlides.slice(1, 4).map((_, idx, arr) => { @@ -97,121 +97,107 @@ export function SidebarBannerCarousel({ slides }: SidebarBannerCarouselProps) { {/* Peek cards above — each one narrower, creating depth perspective */} {peekCount > 0 &&
{peekCards}
} - {/* Front card */} + {/* Front card. The card is the artwork: a brand-tinted panel (card-wash + flips with the theme: cyan-tinted paper in light, cyan-tinted ink in + dark) with the always-on spectrum ring and the triple-band ray + crossing the top corner behind the copy. No raster, so it never + fights the theme it sits in. */}
- {/* Title + description */} -
-
- - {front.title} - - {front.badge && ( + {/* The whole card is the link, but as an overlay sibling rather than a + wrapper: interactive content (the dismiss button) is not allowed + inside an anchor. Copy is pointer-transparent so clicks reach the + overlay; the button opts back in and sits above it. */} + + + + + +
+
+ {front.badge ? ( {front.badge} + ) : ( + )} -
-

{front.description}

-
- - {/* Image preview */} -
- {/* eslint-disable-next-line @next/next/no-img-element */} - {front.visual === "prism" ? ( - // The brand tile: ink panel, the triple-band ray crossing behind a - // small wordmark — the sidebar-scale echo of the reference hero. - // Deliberately ink in both themes (it is artwork, not surface). -
- - - Prisma 8 - -
- ) : front.image ? ( - {front.imageAlt - ) : ( -
+
- )} -
+ +
+ +

+ {front.title} +

+

+ {front.description} +

- {/* Action bar — appears on hover */} -
- - Read more - - + {front.cta ?? "Read more"} + +
- - {/* Bottom padding when action bar is hidden */} -
); diff --git a/apps/docs/src/lib/llms.ts b/apps/docs/src/lib/llms.ts index 9f57e2b6c8..6ec190fa69 100644 --- a/apps/docs/src/lib/llms.ts +++ b/apps/docs/src/lib/llms.ts @@ -171,7 +171,7 @@ export const llmsSections: LLMsSection[] = [ slug: "orm-v7", title: "Prisma ORM v7", description: - "Prisma ORM 7 documentation: the schema.prisma workflow, Prisma Client, Prisma Migrate, the classic prisma CLI, and the Prisma 7 quickstarts and framework guides. Prisma 7 remains fully supported; pin prisma and @prisma/client to 7.9.1.", + "Prisma ORM 7 documentation: the schema.prisma workflow, Prisma Client, Prisma Migrate, the classic prisma CLI, and the Prisma 7 quickstarts and framework guides. Prisma 7 remains fully supported; pin prisma and @prisma/client to 7.10.0.", prefixes: ["/orm/v7", "/v7", "/guides/v7", "/cli/v7"], }, { diff --git a/apps/docs/src/lib/og-image.ts b/apps/docs/src/lib/og-image.ts deleted file mode 100644 index 1e875e8914..0000000000 --- a/apps/docs/src/lib/og-image.ts +++ /dev/null @@ -1,20 +0,0 @@ -/** - * Fetches the og:image URL from a given page URL. - * Returns null if the fetch fails or no og:image is found. - */ -export async function fetchOgImage(url: string): Promise { - try { - const res = await fetch(url, { - next: { revalidate: 86400 }, - signal: AbortSignal.timeout(5000), - }); - if (!res.ok) return null; - const html = await res.text(); - const match = - html.match(/]+property=["']og:image["'][^>]+content=["']([^"']+)["']/i) ?? - html.match(/]+content=["']([^"']+)["'][^>]+property=["']og:image["']/i); - return match?.[1] ?? null; - } catch { - return null; - } -}