fix(generator-prisma-client): bump Prisma version, introduce prisma.config.ts#8260
fix(generator-prisma-client): bump Prisma version, introduce prisma.config.ts#8260
Conversation
…nt-wasm-base64-on-nodejs.6; introduce prisma.config.ts
WalkthroughBumps Prisma packages to 6.14.0 across many templates, adds prisma.config.ts files (with dotenv and migrations/seed settings), removes top-level package.json seed blocks, reorders README steps to generate client before migrate/seed, adds an initial SQLite migration for basic-typedsql, updates Next.js components to call connection(), and refreshes Cloudflare Workerd typings. Changes
Sequence Diagram(s)sequenceDiagram
participant U as User
participant N as Next.js Server
participant S as next/server.connection()
participant P as Prisma Client
participant DB as Database
U->>N: HTTP request (e.g., /quotes)
N->>S: await connection()
S-->>N: connection ready
N->>P: Prisma query (findMany)
P->>DB: SQL
DB-->>P: rows
P-->>N: results
N-->>U: rendered response
sequenceDiagram
participant Dev as Developer
participant CLI as Prisma CLI
participant Cfg as prisma.config.ts
participant DB as Database
Dev->>CLI: prisma generate
CLI->>Cfg: read schema
CLI-->>Dev: client generated
Dev->>CLI: prisma migrate dev --name init
CLI->>Cfg: read migrations path
CLI->>DB: apply migrations
DB-->>CLI: migrated
Dev->>CLI: prisma db seed
CLI->>Cfg: run seed command (tsx/deno)
CLI-->>Dev: seed completed
Suggested reviewers
Tip 🔌 Remote MCP (Model Context Protocol) integration is now available!Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 40
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (20)
generator-prisma-client/basic-typedsql/README.md (4)
11-13: Unify package manager: try-prisma uses npm while the rest of the README uses pnpm.The “Download this example” step installs with npm (
--install npm), but all subsequent commands use pnpm. This is confusing for users and can lead to mismatched lockfiles. Recommend switching to pnpm in the bootstrap command as well.Apply this diff:
-npx try-prisma@latest --template generator-prisma-client/basic-typedsql --install npm --name basic-typedsql +npx try-prisma@latest --template generator-prisma-client/basic-typedsql --install pnpm --name basic-typedsql
29-34: Fix wording: “Install npm dependencies” but the command uses pnpm.To avoid tool confusion, remove the “npm” qualifier in the heading.
-Install npm dependencies: +Install dependencies:
40-44: Table names in the description don’t match the migration/schema (Post vs TrackingEvent).The README says the migration creates
UserandPost, but this template’s migration definesUserandTrackingEvent(per the new migration under prisma/migrations). Please align the docs with the actual schema.-Run the following command to create your SQLite database file. This also creates the `User` and `Post` tables that are defined in [`prisma/schema.prisma`](./prisma/schema.prisma): +Run the following command to create your SQLite database file. This also creates the `User` and `TrackingEvent` tables that are defined in [`prisma/schema.prisma`](./prisma/schema.prisma):If the schema is intended to include
Post, please update the migration and SQL example accordingly instead.
42-44: Optional: drop “--name init” to avoid implying a new migration is created.For a template that already ships with an initial migration,
prisma migrate devwill apply it to a fresh DB. Passing--name initcan be misleading (it won’t be used unless a new migration is actually created). Consider simplifying the command.-pnpm prisma migrate dev --name init +pnpm prisma migrate devgenerator-prisma-client/nextjs-starter-turbopack/components/quotes.tsx (1)
5-9: Pin runtime to Node.js to avoid Prisma/Edge runtime mismatchThis component uses the Node Prisma client (imported from '@/lib/db'). If Next.js deploys this route to the Edge runtime, Prisma will fail. Explicitly pin to Node.js.
Apply this diff:
export const dynamic = 'force-dynamic' export async function Quotes() { + // Ensure Node.js runtime for Prisma Client + // https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes + export const runtime = 'nodejs' await connection()generator-prisma-client/nextjs-starter-webpack-monorepo/README.md (2)
101-105: Optional: Clarify dotenv vs. direnv usage.The examples import 'dotenv/config' in prisma.config.ts (loads .env), while here you recommend .envrc + source. Consider adding a note that a .env file is also supported/expected by the tooling (and may be preferable in CI), or provide a sample .env.
88-95: Critical: Fix duplicated DATABASE_URL in README and align with Prisma schemaThe README currently exports
DATABASE_URLtwice—this causes the migration URL to be overwritten by the client URL. Use a separate environment variable (DIRECT_URL) for the direct connection string and ensure your Prisma schema references both.• In generator-prisma-client/nextjs-starter-webpack-monorepo/README.md (lines 88–95), update the exports:
- # Prisma Postgres connection string (used for migrations) - export DATABASE_URL="__YOUR_PRISMA_POSTGRES_CONNECTION_STRING__" - - # Postgres connection string (used for queries by Prisma Client) - export DATABASE_URL="__YOUR_PRISMA_POSTGRES_DIRECT_CONNECTION_STRING__" + # Prisma Postgres connection string (used for migrations) + export DATABASE_URL="__YOUR_PRISMA_POSTGRES_CONNECTION_STRING__" + + # Direct TCP connection string (used by Prisma Client via datasource.directUrl) + export DIRECT_URL="__YOUR_PRISMA_POSTGRES_DIRECT_CONNECTION_STRING__"• Ensure your Prisma schema (
generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/prisma/schema.prisma) datasource block includes both:datasource db { provider = "postgresql" url = env("DATABASE_URL") directUrl = env("DIRECT_URL") }generator-prisma-client/esbuild-cjs/package.json (1)
8-9: Bug: start:hono runs the minimal script instead of the Hono server.This prevents the intended server entry from starting.
Apply:
- "start:hono": "node -r dotenv/config ./dist/minimal.cjs", + "start:hono": "node -r dotenv/config ./dist/hono.cjs",generator-prisma-client/nextjs-starter-webpack/README.md (1)
55-66: Clarify which environment variables to set.The text says “set the DATABASE_URL environment variables” but you’re setting two variables: DATABASE_URL and DIRECT_URL.
-Now, open the `.env` file and set the `DATABASE_URL` environment variables with the values of your connection string and your Prisma Postgres connection string: +Now, open the `.env` file and set the `DATABASE_URL` and `DIRECT_URL` environment variables with the values of your Prisma Postgres + Accelerate connection string and your direct TCP connection string:generator-prisma-client/react-router-starter-cloudflare-workerd/README.md (2)
3-3: Incorrect framework reference (“Next.js”) in a React Router starter.This should mention React Router, not Next.js.
-This project showcases how to use the Prisma ORM with Prisma Postgres in an ESM Next.js application. +This project showcases how to use the Prisma ORM with Prisma Postgres in an ESM React Router application running on Cloudflare Workerd.
53-61: Clarify env var wording to reflect two variables.Similar to other READMEs, make it explicit that both DATABASE_URL and DIRECT_URL are being set.
-Now, open the `.env` file and set the `DATABASE_URL` environment variables with the values of your connection string and your Prisma Postgres connection string: +Now, open the `.env` file and set the `DATABASE_URL` and `DIRECT_URL` environment variables with the values of your Prisma Postgres + Accelerate connection string and your direct TCP connection string:generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/package.json (3)
22-38: Incorrect exports field structure (nested “import” object).Node’s package “exports” map should not nest an object under the “import” key. This will break module resolution. Flatten to standard keys: types, import, default.
"exports": { ".": { - "import": { - "@prisma/source": "./src/index.ts", - "types": "./dist/index.d.ts", - "import": "./dist/index.js", - "default": "./dist/index.js" - } + "types": "./dist/index.d.ts", + "import": "./dist/index.js", + "default": "./dist/index.js" }, "./enums": { - "import": { - "types": "./dist/enums.d.ts", - "import": "./dist/enums.js", - "default": "./dist/enums.js" - } + "types": "./dist/enums.d.ts", + "import": "./dist/enums.js", + "default": "./dist/enums.js" } },
8-12: repository.directory points to “packages/db” but this package is “packages/prisma”.Fix the path so links and npm metadata are accurate.
"repository": { "type": "git", "url": "https://github.com/prisma/prisma-examples.git", - "directory": "generator-prisma-client/nextjs-starter-webpack-monorepo/packages/db" + "directory": "generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma" },
39-43: Consider exposing a seed script in this package (optional).Given tsx is present and seeds exist in this monorepo, adding a “seed” npm script can improve DX, e.g., "seed": "prisma db seed".
"scripts": { "clean": "rm -rf dist && rm -rf ./src/.generated", "generate": "prisma generate", - "build": "tsc" + "build": "tsc", + "seed": "prisma db seed" },generator-prisma-client/nextjs-starter-turbopack/package.json (2)
2-2: Package name references “webpack” but this is the turbopack starter.Likely a copy-paste error; rename to avoid confusion in registries and tooling.
- "name": "generator-prisma-client-nextjs-starter-webpack", + "name": "generator-prisma-client-nextjs-starter-turbopack",
6-10: repository.directory points to the webpack starter path.Should point to nextjs-starter-turbopack.
"repository": { "type": "git", "url": "https://github.com/prisma/prisma-examples.git", - "directory": "generator-prisma-client/nextjs-starter-webpack" + "directory": "generator-prisma-client/nextjs-starter-turbopack" },generator-prisma-client/nextjs-starter-webpack-turborepo/README.md (3)
58-66: Fix path to Prisma schema file: package is “database”, not “prisma”.The project structure shows packages/database, so the schema link should match.
- See the [Prisma schema file](./packages/prisma/prisma/schema.prisma) for details. + See the [Prisma schema file](./packages/database/prisma/schema.prisma) for details.
134-144: Fix paths for schema and seed references to use “packages/database”.Both links currently point to packages/prisma.
-The [Prisma schema file](./packages/prisma/prisma/schema.prisma) contains a single `Quotes` model and a `QuoteKind` enum. You can map this model to the database and create the corresponding `Quotes` table using the following command: +The [Prisma schema file](./packages/database/prisma/schema.prisma) contains a single `Quotes` model and a `QuoteKind` enum. You can map this model to the database and create the corresponding `Quotes` table using the following command: -You now have an empty `Quotes` table in your database. Next, run the [seed script](./packages/prisma/prisma/seed.ts) to create some sample records in the table: +You now have an empty `Quotes` table in your database. Next, run the [seed script](./packages/database/prisma/seed.ts) to create some sample records in the table:
146-152: Section numbering jumps from 4 to 7.Renumber “Start the Next.js app” to follow previous steps.
-### 7. Start the Next.js app +### 5. Start the Next.js appgenerator-prisma-client/react-router-starter-cloudflare-workerd/package.json (1)
13-18: Use a consistent script runner (pnpm) in scriptsThis package declares pnpm in packageManager and elsewhere; using
npm runhere is inconsistent and can confuse CI and contributors.Apply this diff:
- "deploy": "pnpm run build && wrangler deploy", + "deploy": "pnpm run build && wrangler deploy", "dev": "react-router dev", - "postinstall": "npm run cf-typegen", - "preview": "pnpm run build && vite preview", - "typecheck": "npm run cf-typegen && react-router typegen && tsc -b" + "postinstall": "pnpm run cf-typegen", + "preview": "pnpm run build && vite preview", + "typecheck": "pnpm run cf-typegen && react-router typegen && tsc -b"
♻️ Duplicate comments (3)
generator-prisma-client/nextjs-starter-turbopack/prisma.config.ts (1)
1-10: Mirror of the esbuild-cjs config; same checks apply.The structure matches the other prisma.config.ts files. Ensure local deps (dotenv, tsx) exist as referenced and that CLI 6.14.0 picks up migrations.seed.
You can reuse the verification script from the esbuild-cjs comment to validate dotenv/tsx presence across all configs.
generator-prisma-client/nuxt3-starter-nodejs/prisma.config.ts (1)
8-8: Same tsx dependency check as the other templates.Ensure
tsxis present soprisma db seeddoesn’t fail at runtime.generator-prisma-client/deno-deploy/prisma.config.ts (1)
1-13: Thanks for adding dotenv/config; this addresses the env loading issue raised earlierThe side-effect import ensures .env is loaded when Prisma CLI runs and the spawned deno seed inherits those vars. The inline comment with the Deno issue link is helpful.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (30)
generator-prisma-client/basic-typedsql/pnpm-lock.yamlis excluded by!**/pnpm-lock.yamlgenerator-prisma-client/deno-deploy/deno.lockis excluded by!**/*.lockgenerator-prisma-client/esbuild-cjs/pnpm-lock.yamlis excluded by!**/pnpm-lock.yamlgenerator-prisma-client/nextjs-starter-turbopack/pnpm-lock.yamlis excluded by!**/pnpm-lock.yamlgenerator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/client.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/internal/class.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/internal/prismaNamespace.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/models/Quotes.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-monorepo/pnpm-lock.yamlis excluded by!**/pnpm-lock.yamlgenerator-prisma-client/nextjs-starter-webpack-turborepo/pnpm-lock.yamlis excluded by!**/pnpm-lock.yamlgenerator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma-edge/client.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma-edge/commonInputTypes.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma-edge/enums.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma-edge/internal/class.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma-edge/internal/prismaNamespace.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma-edge/libquery_engine-darwin-arm64.dylib.nodeis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma-edge/models.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma-edge/models/Quotes.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma/client.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma/commonInputTypes.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma/enums.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma/internal/class.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma/internal/prismaNamespace.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma/models.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/lib/generated/prisma/models/Quotes.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-with-middleware/pnpm-lock.yamlis excluded by!**/pnpm-lock.yamlgenerator-prisma-client/nextjs-starter-webpack/pnpm-lock.yamlis excluded by!**/pnpm-lock.yamlgenerator-prisma-client/nuxt3-starter-nodejs/pnpm-lock.yamlis excluded by!**/pnpm-lock.yamlgenerator-prisma-client/react-router-starter-cloudflare-workerd/pnpm-lock.yamlis excluded by!**/pnpm-lock.yamlgenerator-prisma-client/react-router-starter-nodejs/pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (45)
generator-prisma-client/basic-typedsql/README.md(1 hunks)generator-prisma-client/basic-typedsql/package.json(1 hunks)generator-prisma-client/basic-typedsql/prisma/migrations/20250820114100_init/migration.sql(1 hunks)generator-prisma-client/basic-typedsql/prisma/migrations/migration_lock.toml(1 hunks)generator-prisma-client/deno-deploy/README.md(1 hunks)generator-prisma-client/deno-deploy/deno.jsonc(1 hunks)generator-prisma-client/deno-deploy/prisma.config.ts(1 hunks)generator-prisma-client/esbuild-cjs/README.md(1 hunks)generator-prisma-client/esbuild-cjs/package.json(1 hunks)generator-prisma-client/esbuild-cjs/prisma.config.ts(1 hunks)generator-prisma-client/nextjs-starter-turbopack/README.md(1 hunks)generator-prisma-client/nextjs-starter-turbopack/components/quotes.tsx(2 hunks)generator-prisma-client/nextjs-starter-turbopack/package.json(2 hunks)generator-prisma-client/nextjs-starter-turbopack/prisma.config.ts(1 hunks)generator-prisma-client/nextjs-starter-webpack-monorepo/README.md(1 hunks)generator-prisma-client/nextjs-starter-webpack-monorepo/packages/next-app/components/quotes.tsx(2 hunks)generator-prisma-client/nextjs-starter-webpack-monorepo/packages/next-app/package.json(0 hunks)generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/package.json(1 hunks)generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/prisma.config.ts(1 hunks)generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/seed.ts(1 hunks)generator-prisma-client/nextjs-starter-webpack-turborepo/.envrc.example(0 hunks)generator-prisma-client/nextjs-starter-webpack-turborepo/.gitignore(1 hunks)generator-prisma-client/nextjs-starter-webpack-turborepo/README.md(2 hunks)generator-prisma-client/nextjs-starter-webpack-turborepo/apps/web/components/quotes.tsx(2 hunks)generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json(2 hunks)generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/prisma.config.ts(1 hunks)generator-prisma-client/nextjs-starter-webpack-turborepo/turbo.json(2 hunks)generator-prisma-client/nextjs-starter-webpack-with-middleware/.gitignore(1 hunks)generator-prisma-client/nextjs-starter-webpack-with-middleware/README.md(1 hunks)generator-prisma-client/nextjs-starter-webpack-with-middleware/components/quotes.tsx(2 hunks)generator-prisma-client/nextjs-starter-webpack-with-middleware/package.json(2 hunks)generator-prisma-client/nextjs-starter-webpack-with-middleware/prisma.config.ts(1 hunks)generator-prisma-client/nextjs-starter-webpack/README.md(1 hunks)generator-prisma-client/nextjs-starter-webpack/components/quotes.tsx(2 hunks)generator-prisma-client/nextjs-starter-webpack/package.json(2 hunks)generator-prisma-client/nextjs-starter-webpack/prisma.config.ts(1 hunks)generator-prisma-client/nuxt3-starter-nodejs/package.json(1 hunks)generator-prisma-client/nuxt3-starter-nodejs/prisma.config.ts(1 hunks)generator-prisma-client/react-router-starter-cloudflare-workerd/README.md(1 hunks)generator-prisma-client/react-router-starter-cloudflare-workerd/package.json(2 hunks)generator-prisma-client/react-router-starter-cloudflare-workerd/prisma.config.ts(1 hunks)generator-prisma-client/react-router-starter-cloudflare-workerd/worker-configuration.d.ts(19 hunks)generator-prisma-client/react-router-starter-nodejs/README.md(1 hunks)generator-prisma-client/react-router-starter-nodejs/package.json(2 hunks)generator-prisma-client/react-router-starter-nodejs/prisma.config.ts(1 hunks)
💤 Files with no reviewable changes (2)
- generator-prisma-client/nextjs-starter-webpack-monorepo/packages/next-app/package.json
- generator-prisma-client/nextjs-starter-webpack-turborepo/.envrc.example
🧰 Additional context used
🪛 LanguageTool
generator-prisma-client/nextjs-starter-webpack-monorepo/README.md
[grammar] ~107-~107: Use correct spacing
Context: ...envrc ### 3. Generate Prisma Client Run: pnpm --filter @nextjs-starter-...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~109-~109: Use correct spacing
Context: ... ### 3. Generate Prisma Client Run: pnpm --filter @nextjs-starter-webpack-monorepo/prisma exec prisma generate ``` ### 4. Run a migration to create the databas...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~115-~115: There might be a mistake here.
Context: ...database structure and seed the database The [Prisma schema file](./packages/pris...
(QB_NEW_EN_OTHER)
generator-prisma-client/esbuild-cjs/README.md
[grammar] ~78-~78: Use correct spacing
Context: ...tabase>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~80-~80: Use correct spacing
Context: ...>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### 4. Run a migration to create the databas...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~86-~86: There might be a mistake here.
Context: ...database structure and seed the database The [Prisma schema file](./prisma/schema...
(QB_NEW_EN_OTHER)
[grammar] ~88-~88: Use correct spacing
Context: ...otestable using the following command: ``` pnpm prisma migrate dev --name init ``` You now have an emptyQuotes` table in ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~94-~94: Use correct spacing
Context: ...create some sample records in the table: pnpm prisma db seed ### 5. Bundle the project Run ``` pnpm bun...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
generator-prisma-client/nextjs-starter-webpack-with-middleware/README.md
[grammar] ~81-~81: Use correct spacing
Context: ...tabase>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~83-~83: Use correct spacing
Context: ...>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### 4. Run a migration to create the databas...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~89-~89: There might be a mistake here.
Context: ...database structure and seed the database The [Prisma schema file](./prisma/schema...
(QB_NEW_EN_OTHER)
[grammar] ~91-~91: Use correct spacing
Context: ...otestable using the following command: ``` pnpm prisma migrate dev --name init ``` You now have an emptyQuotes` table in ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~97-~97: Use correct spacing
Context: ...create some sample records in the table: pnpm prisma db seed ### 5. Start the app You can run the app wi...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
generator-prisma-client/nextjs-starter-webpack-turborepo/README.md
[grammar] ~83-~83: Use correct spacing
Context: ...le in the packages/database directory: bash cd packages/database; touch .env Now, open the .env file and set the `D...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~89-~89: Use correct spacing
Context: ... your Prisma Postgres connection string: bash # packages/database/.env # Prisma Postgres connection string (used for migrations) DATABASE_URL="__YOUR_PRISMA_POSTGRES_CONNECTION_STRING__" # Postgres connection string (used for queries by Prisma Client) DIRECT_URL="__YOUR_PRISMA_POSTGRES_DIRECT_CONNECTION_STRING__" NEXT_PUBLIC_URL="http://localhost:3000" Then, create an .env file in the `apps...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~103-~103: Use correct spacing
Context: ....env file in the apps/web directory: bash cd apps/web; touch .env Now, open the .env file and set the `D...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~109-~109: Use correct spacing
Context: ... your Prisma Postgres connection string: bash # apps/web/.env # Postgres connection string (used for queries by Prisma Client) DIRECT_URL="__YOUR_PRISMA_POSTGRES_DIRECT_CONNECTION_STRING__" NEXT_PUBLIC_URL="http://localhost:3000" Note that `__YOUR_PRISMA_POSTGRES_CONNEC...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~124-~124: There might be a mistake here.
Context: ...ld the Prisma Client and the Next.js app Run: pnpm build ### 4. Run a m...
(QB_NEW_EN_OTHER)
[grammar] ~126-~126: Use correct spacing
Context: ... Prisma Client and the Next.js app Run: pnpm build ### 4. Run a migration to create the databas...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~132-~132: There might be a mistake here.
Context: ...database structure and seed the database The [Prisma schema file](./packages/pris...
(QB_NEW_EN_OTHER)
generator-prisma-client/deno-deploy/README.md
[grammar] ~66-~66: Use correct spacing
Context: ...tabase>`. ### 3. Generate Prisma Client Run: deno task prisma generate ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~68-~68: Use correct spacing
Context: ...>`. ### 3. Generate Prisma Client Run: deno task prisma generate ### 4. Run a migration to create the databas...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~74-~74: There might be a mistake here.
Context: ...database structure and seed the database The [Prisma schema file](./prisma/schema...
(QB_NEW_EN_OTHER)
[grammar] ~76-~76: Use correct spacing
Context: ...otestable using the following command: ``` deno task prisma migrate dev --name init ``` You now have an emptyQuotes` table in ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~82-~82: Use correct spacing
Context: ...create some sample records in the table: deno task prisma db seed ### 5. Start the app You can run the app wi...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
generator-prisma-client/nextjs-starter-turbopack/README.md
[grammar] ~73-~73: Use correct spacing
Context: ...tabase>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~75-~75: Use correct spacing
Context: ...>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### 4. Run a migration to create the databas...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~81-~81: There might be a mistake here.
Context: ...database structure and seed the database The [Prisma schema file](./prisma/schema...
(QB_NEW_EN_OTHER)
[grammar] ~83-~83: Use correct spacing
Context: ...otestable using the following command: ``` pnpm prisma migrate dev --name init ``` You now have an emptyQuotes` table in ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~89-~89: Use correct spacing
Context: ...create some sample records in the table: pnpm prisma db seed ### 5. Start the app You can run the app wi...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
generator-prisma-client/react-router-starter-cloudflare-workerd/README.md
[grammar] ~82-~82: Use correct spacing
Context: ...tabase>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~84-~84: Use correct spacing
Context: ...>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### 4. Run a migration to create the databas...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~90-~90: There might be a mistake here.
Context: ...database structure and seed the database The [Prisma schema file](./prisma/schema...
(QB_NEW_EN_OTHER)
[grammar] ~92-~92: Use correct spacing
Context: ...otestable using the following command: ``` pnpm prisma migrate dev --name init ``` You now have an emptyQuotes` table in ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~98-~98: Use correct spacing
Context: ...create some sample records in the table: pnpm prisma db seed ### 5. Start the app You can run the app wi...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
generator-prisma-client/nextjs-starter-webpack/README.md
[grammar] ~73-~73: Use correct spacing
Context: ...tabase>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~75-~75: Use correct spacing
Context: ...>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### 4. Run a migration to create the databas...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~81-~81: There might be a mistake here.
Context: ...database structure and seed the database The [Prisma schema file](./prisma/schema...
(QB_NEW_EN_OTHER)
[grammar] ~83-~83: Use correct spacing
Context: ...otestable using the following command: ``` pnpm prisma migrate dev --name init ``` You now have an emptyQuotes` table in ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~89-~89: Use correct spacing
Context: ...create some sample records in the table: pnpm prisma db seed ### 5. Start the app You can run the app wi...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
generator-prisma-client/react-router-starter-nodejs/README.md
[grammar] ~70-~70: Use correct spacing
Context: ...tabase>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~72-~72: Use correct spacing
Context: ...>`. ### 3. Generate Prisma Client Run: pnpm prisma generate ### 4. Run a migration to create the databas...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~78-~78: There might be a mistake here.
Context: ...database structure and seed the database The [Prisma schema file](./prisma/schema...
(QB_NEW_EN_OTHER)
[grammar] ~80-~80: Use correct spacing
Context: ...otestable using the following command: ``` pnpm prisma migrate dev --name init ``` You now have an emptyQuotes` table in ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
[grammar] ~86-~86: Use correct spacing
Context: ...create some sample records in the table: pnpm prisma db seed ### 5. Start the app You can run the app wi...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
🪛 markdownlint-cli2 (0.17.2)
generator-prisma-client/nextjs-starter-webpack-monorepo/README.md
107-107: Files should end with a single newline character
(MD047, single-trailing-newline)
generator-prisma-client/nextjs-starter-webpack-with-middleware/README.md
85-85: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
93-93: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
99-99: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
generator-prisma-client/nextjs-starter-webpack-turborepo/README.md
128-128: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
generator-prisma-client/deno-deploy/README.md
75-75: Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
generator-prisma-client/react-router-starter-cloudflare-workerd/README.md
86-86: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
94-94: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
100-100: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
generator-prisma-client/nextjs-starter-webpack/README.md
77-77: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
85-85: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
91-91: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🪛 Biome (2.1.2)
generator-prisma-client/react-router-starter-cloudflare-workerd/worker-configuration.d.ts
[error] 6800-6800: An empty interface is equivalent to {}.
Safe fix: Use a type alias instead.
(lint/suspicious/noEmptyInterface)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: test (orm/grpc)
🔇 Additional comments (62)
generator-prisma-client/react-router-starter-cloudflare-workerd/worker-configuration.d.ts (15)
1-4: Generated types version bump: verify Wrangler/workerd alignmentHeader shows workerd runtime types updated to 1.20250803.0 (2025-04-04). Ensure:
- wrangler version in these examples produces the same types locally
- CI uses a compatible toolchain (wrangler/workerd) to avoid drift
If needed, I can add a quick matrix check in CI to assert the generated types’ hash matches across environments.
1108-1149: New MessageEvent API surface addedAdds
MessageEventandMessageEventInitalong with MessagePort (see below). This mirrors standard web APIs and should not be an issue, but if any consumer declared customMessageEventtypes, name collisions could occur.No action needed unless you defined your own MessageEvent in examples.
2518-2549: Channel Messaging API added (MessagePort, postMessage options)New types for
MessagePortandMessagePortPostMessageOptions. Good addition; no breaking changes expected.
5324-5324: AI API growth: new Ai.autorag() helper
Ai#autorag(autoragId?)added. It’s additive and safe. Ensure examples don’t imply availability where bindings aren’t configured.If you want, I can scan examples for
autorag(usage to confirm none were added inadvertently.
6495-6507: ImageTransform.trim expanded with detailed border optionsAdditive change, backwards compatible. If you rely on
trim: "border", nothing to do.
6518-6519: New ImageInputOptions { encoding?: 'base64' }Additive. Enables base64 input handling; see updated ImagesBinding signatures.
6561-6562: ImageTransformation output: base64 encoding option and updated image() signature
ImageTransformationResult.image(options?)now accepts{ encoding?: 'base64' }. Backwards compatible (param is optional).Also applies to: 6575-6576
6886-6887: cloudflare:workers now exports waitUntil()Small ergonomic win; additive. No changes required in examples using
ctx.waitUntil.
7041-7061: Verify existing tail/tailStream handlers before migrationOur search only found the new type definitions in
• generator-prisma-client/react-router-starter-cloudflare-workerd/worker-configuration.d.ts (lines 361–364 definetail?: …andtailStream?: …)No other references to
tailStreamor calls totail(appeared in.ts/.tsxfiles. Please manually verify that you don’t have:
- Custom
tailortailStreamhandlers in your codebase (including any.jsor generated files)- Any usage of the old handler signature that needs to be updated
If you do have existing handlers, update them to return a
TailEventHandlerObject(e.g.{ log(event) {…}, outcome(e) {…}, … }) so they work with the new genericTailEventmodel.
1457-1457: No Service usages detected; no type breakages expectedI searched the entire codebase for
Service<…>and only found its definition inworker-configuration.d.ts—no call sites exist. Since there are no existing uses, expanding the conditional type won’t affect any code.
355-355: Breaking change:tailStreamhandlers now only receiveOnseteventsThe signature of
ExportedHandlerTailStreamHandler<Env>has been narrowed from the non-genericTailStream.TailEventtoTailStream.TailEvent<TailStream.Onset>. If you have anytailStreamhandlers in your code, they will no longer receive other event kinds by default.Actions:
- Search your codebase for any existing
tailStream:handler implementations.- Update those handlers to expect only onset events (e.g. check
event.event.type === "onset").- If you need to handle other TailStream event types in the future, migrate to the new per-event mapping using
TailEventHandlerObject.
5968-5968: No existing references torequest.cf.hostMetadata—no guards needed
Verified thathostMetadatais now optional in the type definitions, and there are no occurrences ofrequest.cf.hostMetadatain any.tsor.tsxfiles. No changes are required at this time. If you add code that accesseshostMetadatain the future, wrap it in an undefined check.
6531-6538: No example usages ofimages.input/images.infofound
I’ve searched all .ts, .tsx, .js, .jsx, and .md files for calls toimages.input(orimages.info(and found no occurrences. No example code changes or docs updates are needed.
6909-6909: No cfJson usages detected – change is safeAfter searching the entire codebase, there are zero references or property accesses to
cfJson. This widening of the type toobject(and making it optional) does not affect any existing code here, so you can disregard the previous warning about string operations or undefined guards.Likely an incorrect or invalid review comment.
5838-5845: No internal references to updated CF properties
A search across all .ts/.tsx files found no directrequest.cf.asnorrequest.cf.asOrganizationaccesses. There’s no code here that needs to be wrapped in optional chaining or defaulted.Action items:
- Add a CHANGELOG (or migration guide) entry noting that
cf.asnandcf.asOrganizationare now optional.- Advise external consumers to use optional chaining or provide defaults when reading these properties.
generator-prisma-client/basic-typedsql/README.md (1)
61-63: Run command switch to pnpm is correct and consistent with scripts.The README now uses
pnpm dev, which matches the package’s scripts and packageManager. No issues here.generator-prisma-client/basic-typedsql/package.json (2)
16-16: Version bump to @prisma/client 6.14.0 looks good.Matches the CLI version in devDependencies; keeps client/CLI in lockstep.
20-20: Prisma CLI bumped to 6.14.0 — consistent with client dependency.No action needed.
generator-prisma-client/nextjs-starter-webpack-with-middleware/components/quotes.tsx (2)
5-8: Placement ofawait connection()before Prisma query is appropriate.Assuming the API is supported, this executes before the Prisma call and complements
dynamic = 'force-dynamic'to avoid stale data. Looks good.Also applies to: 10-15
1-1: Ensureconnection()aligns with your Next.js versionNext.js v15.0.0+ officially exports
connection()fromnext/server, letting you callawait connection()inside Server Components. If your project is on Next.js 14.x or earlier, continue using the legacy API (unstable_noStore) orexport const dynamic = 'force-dynamic'instead—connection()isn’t available until v15.• Affected file:
– generator-prisma-client/nextjs-starter-webpack-with-middleware/components/quotes.tsx (import at line 1)No changes required if you’re on v15+. Otherwise, fall back to the v14 patterns or upgrade to v15 to use
connection().generator-prisma-client/nextjs-starter-webpack-monorepo/packages/next-app/components/quotes.tsx (2)
5-8: No issues with the sequencing.
await connection()precedes the Prisma query anddynamic = 'force-dynamic'is set. No further changes needed.Also applies to: 10-15
1-1: Ensure Next.js v15+ forconnection()usage
Theconnection()helper is officially documented for Server Components and has been available since Next.js v15.0.0 (stabilized after the RC release). Please confirm that:
packages/next-appdepends on Next.js >= 15.0.0- Any other Next.js apps in the monorepo also target v15+
If any are on earlier versions, upgrade to v15+ or fall back to the prior API (e.g.,
unstable_noStore).generator-prisma-client/nextjs-starter-webpack-turborepo/apps/web/components/quotes.tsx (2)
5-8: LGTM on call order and dynamic rendering.The call to
await connection()is correctly placed ahead of the Prisma query;dynamic = 'force-dynamic'is set to avoid caching issues.Also applies to: 10-15
1-1: Remove non-existentconnection()import fromnext/serverNext.js does not export a
connection()helper fromnext/server(App Router/RSC or route handlers). You’ll need to remove this import and replace it with your own database-connection logic (e.g. Prisma client, custom helper, etc.).Locations to update:
- apps/web/components/quotes.tsx:
- Line 1: remove
import { connection } from 'next/server'- Line 10: remove or replace any calls to
connection()Example diff:
--- a/apps/web/components/quotes.tsx +++ b/apps/web/components/quotes.tsx @@ -1,1 +0,0 @@ -import { connection } from 'next/server' @@ -10,10 +9,11 @@ - const db = connection() + // TODO: initialize your database connection here, e.g.: + // import { prisma } from '~/server/db' + // const db = prismaLikely an incorrect or invalid review comment.
generator-prisma-client/react-router-starter-cloudflare-workerd/prisma.config.ts (1)
4-10: LGTM: Prisma config + dotenv bootstrap look correctSchema, migrations path, and seed command are consistent with the PR’s pattern. Importing
dotenv/configensures envs are loaded when the Prisma CLI evaluates this file.generator-prisma-client/deno-deploy/deno.jsonc (2)
13-17: LGTM: Prisma + adapter upgrades and dotenv import mapThe version bumps align with the PR-wide update and should keep the Deno example consistent with the new Prisma toolchain.
4-9: ConfirmprismaCLI invocation works under Deno tasks in fresh environmentsDeno tasks call
prismadirectly. Depending on developer setup, this may require NPM integration to resolve the CLI. Consider making it explicit.
- If you’ve verified Deno resolves the
prismaCLI fine as-is, ignore this.- Otherwise, an explicit task can be used:
Example (outside the changed lines, for illustration):
"tasks": { "prisma": "deno run -A npm:prisma", "prisma:generate": "deno run -A npm:prisma generate", "prisma:migrate": "deno run -A npm:prisma migrate deploy" }generator-prisma-client/react-router-starter-nodejs/package.json (2)
12-13: Seeding configuration verified in prisma.config.ts
- Found at generator-prisma-client/react-router-starter-nodejs/prisma.config.ts
- Includes
import 'dotenv/config'- Defines
migrations.seedas'tsx ./prisma/seed.ts'No further action needed.
12-13: No further action needed: Prisma versions are consistent across generator-prisma-client templatesI verified that every
generator-prisma-client/**/package.jsonin this PR pins both@prisma/clientandprismato version 6.14.0. No mismatches were found.generator-prisma-client/nextjs-starter-webpack/components/quotes.tsx (1)
1-1: All Verified:connection()andcreatedAtField Confirmed
- nextjs-starter-webpack is on Next.js v15.3.5, which exports
connectionfromnext/serverconnection()is imported and used incomponents/quotes.tsx- The Prisma model
Quotesinschema.prismadefines acreatedAtDateTime fieldNo changes needed here.
generator-prisma-client/basic-typedsql/prisma/migrations/migration_lock.toml (1)
1-3: Lock file provider matches schema datasource providerThe
migration_lock.tomlspecifiesprovider = "sqlite"and thedatasource dbingenerator-prisma-client/basic-typedsql/prisma/schema.prismaalso usesprovider = "sqlite". No changes are needed.generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/prisma.config.ts (1)
5-8: Prerequisites forprismaseed command verified
tsx(v4.20.3) is declared in bothpackages/prisma/package.jsonandpackages/next-app/package.jsonsrc/seed.tsexists atpackages/prisma/src/seed.tsprisma/migrationsdirectory isn’t present yet (it will be created byprisma migrate)All prerequisites are satisfied.
generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/seed.ts (1)
1-3: Module paths verified
generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/enums.tsre-exportsQuoteKindfrom./generated/prisma/enums.generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/index.tsexportsgetDbas expected.Imports in
seed.tsare correctly resolving; no changes needed.generator-prisma-client/esbuild-cjs/prisma.config.ts (1)
1-10: Prisma Config & Dependencies Check Complete
- All Node-based generators (e.g. esbuild-cjs, basic-typedsql, Next.js starters) import
dotenv/configand usetsxin their seed commands, and each hasdotenvandtsxdeclared in its package.json.- The Deno-deploy generator omits package.json by design (uses
deno run), so no Node deps should be added there.Next step: please verify that Prisma CLI v6.14.0 recognizes
prisma.config.tswith amigrations.seedproperty (seed commands defined in the config) as expected.generator-prisma-client/nextjs-starter-webpack-with-middleware/package.json (1)
27-29: Version bumps and dotenv addition look correct for the new prisma.config.ts flow.Upgrading @prisma/* to 6.14.0 and adding dotenv aligns with importing 'dotenv/config' from prisma.config.ts. No concerns here.
Also applies to: 44-44, 47-47
generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json (1)
22-23: Dependency upgrades LGTM.@prisma/adapter-pg, @prisma/client, and prisma aligned on 6.14.0. dotenv added as suggested by the new config usage. Looks good.
Also applies to: 28-28, 30-30
generator-prisma-client/basic-typedsql/prisma/migrations/20250820114100_init/migration.sql (1)
14-14: Confirm desired delete semantics for TrackingEvent → User.ON DELETE RESTRICT prevents deleting a user that has events. If you expect user deletion to cascade to their events, switch to CASCADE. If events should be retained, RESTRICT is fine, but consider documenting it to avoid surprises.
Alternative (only if cascade is intended):
-CONSTRAINT "TrackingEvent_userId_fkey" FOREIGN KEY ("userId") REFERENCES "User" ("id") ON DELETE RESTRICT ON UPDATE CASCADE +CONSTRAINT "TrackingEvent_userId_fkey" FOREIGN KEY ("userId") REFERENCES "User" ("id") ON DELETE CASCADE ON UPDATE CASCADEgenerator-prisma-client/nextjs-starter-webpack-with-middleware/prisma.config.ts (1)
1-10: Seed runner availability confirmed
generator-prisma-client/nextjs-starter-webpack-with-middleware/package.jsonalready includestsx@4.20.3underdevDependencies, so theseed: 'tsx ./prisma/seed.ts'command will resolve correctly. No changes are required.generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/prisma.config.ts (1)
1-10: tsx devDependency verified in packages/databaseThe
packages/database/package.jsonalready includestsx@4.19.1underdevDependencies, so theseed: 'tsx ./src/seed.ts'command will run as expected.generator-prisma-client/nextjs-starter-webpack-turborepo/turbo.json (1)
13-19: Confirm caching intent for db:migrate:dev.You removed
"cache": falsefromdb:migrate:devwhile other db tasks still disable caching. If this wasn’t intentional, re-add it to prevent stale caches from skipping migrations.Proposed change (if needed):
"db:migrate:dev": { - "env": ["DATABASE_URL", "DIRECT_URL"], + "env": ["DATABASE_URL", "DIRECT_URL"], + "cache": false, "inputs": [ "packages/database/**" ], "persistent": true },generator-prisma-client/deno-deploy/README.md (1)
66-72: Fix spacing around code fence in Step 3.Add a blank line before the code block for readability and markdownlint compliance.
-Run: +Run: +deno task prisma generate
Likely an incorrect or invalid review comment.
generator-prisma-client/react-router-starter-nodejs/prisma.config.ts (2)
4-10: Prisma config is consistent and clear.Config shape, dotenv preload, and local schema/migrations paths look correct and align with Prisma 6’s prisma.config.ts.
8-8: tsx Dependency VerifiedThe seed command in
generator-prisma-client/react-router-starter-nodejs/prisma.config.tsrelies ontsx, andgenerator-prisma-client/react-router-starter-nodejs/package.jsonalready declares"tsx"in its dependencies. No further action is needed.generator-prisma-client/esbuild-cjs/README.md (1)
78-99: Generating Prisma Client before migrate/seed is a good flow.Reordering to “generate → migrate → seed” improves clarity and avoids first-run friction when code imports the client before the database exists.
generator-prisma-client/nuxt3-starter-nodejs/prisma.config.ts (1)
4-10: Config looks right and matches the pattern used across templates.Schema/migrations paths and dotenv preload are sensible defaults.
generator-prisma-client/react-router-starter-nodejs/README.md (1)
70-91: Client-first flow LGTM.Generating the client before running migrations is fine and aligns with the updated Prisma setup.
generator-prisma-client/esbuild-cjs/package.json (2)
16-29: Prisma version bumps look consistent and appropriate.Dependencies and CLI are aligned on 6.14.0. dotenv/tsx versions are reasonable for this template.
8-12: All sibling packages verified: no additionalstart:honomiswires foundRan a repository-wide scan for other
start:honoscripts pointing tominimal.cjsundergenerator-prisma-client/**/package.jsonand found only the one inesbuild-cjs/package.json. No further copy/paste slips detected.generator-prisma-client/nextjs-starter-webpack-with-middleware/README.md (1)
81-101: Prisma config and seed script properly configured
Theprisma.config.tsin this starter correctly references./prisma/schema.prismaand setsmigrations.seedtotsx ./prisma/seed.ts. No further changes needed here.generator-prisma-client/nextjs-starter-turbopack/README.md (1)
73-93: Verified prisma.config.ts seed configurationThe
prisma.config.tsfile is present at
generator-prisma-client/nextjs-starter-turbopack/prisma.config.ts
and correctly defines:
schema: './prisma/schema.prisma'migrations.seed: 'tsx ./prisma/seed.ts'The README’s instructions for
pnpm prisma migrate dev --name initandpnpm prisma db seedare therefore accurate. No changes needed.generator-prisma-client/nuxt3-starter-nodejs/package.json (2)
13-15: Version bumps look correct and consistent across @prisma/ dependencies*Upgrading @prisma/adapter-pg and @prisma/client to 6.14.0 is consistent with the repo-wide change.
21-23: dotenv usage confirmed in prisma.config.tsThe file
generator-prisma-client/nuxt3-starter-nodejs/prisma.config.tsincludes the side-effect importimport 'dotenv/config'which ensures Prisma CLI and the seed command inherit environment variables.
generator-prisma-client/nextjs-starter-webpack/package.json (2)
27-29: Version bumps to 6.14.0 and dotenv addition look correctThe dependency set aligns with the new Prisma CLI/config approach.
43-47: dotenv Support Verified in prisma.config.tsConfirmed that
generator-prisma-client/nextjs-starter-webpack/prisma.config.tsalready includes:import 'dotenv/config'No changes are needed.
generator-prisma-client/nextjs-starter-webpack/README.md (1)
73-94: Flow reordering to “Generate → Migrate → Seed” looks good.This matches the new prisma.config.ts-driven seed workflow and reduces first-run friction.
generator-prisma-client/react-router-starter-cloudflare-workerd/README.md (1)
82-102: Client-first flow (generate → migrate → seed) looks correct for the workerd runtime.Matches generator runtime "workerd" in schema and aligns with prisma.config.ts seeding.
generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/package.json (1)
45-54: Version bumps to Prisma 6.14.0 look good.Dependencies and devDependencies are aligned; adding tsx is appropriate for seeding/tooling.
generator-prisma-client/nextjs-starter-turbopack/package.json (1)
27-47: Prisma version bump and dotenv addition look good.Dependencies align across @prisma/adapter-pg, @prisma/client, and prisma. dotenv in devDependencies matches the prisma.config.ts side-effect import strategy.
generator-prisma-client/nextjs-starter-webpack-turborepo/README.md (1)
83-116: Overall env splitting between packages/database and apps/web looks good.Clear separation helps local dev and aligns with Turborepo task inputs in turbo.json.
generator-prisma-client/react-router-starter-cloudflare-workerd/package.json (3)
36-36: CLI bumped to prisma 6.14.0 — OKKeeping CLI and client in lockstep avoids subtle mismatches during generate/migrate.
35-35: dotenv version validatedThe specified
dotenv@17.2.0 is published on npm (latest is 17.2.1), so no change is needed.
20-21: Prisma config & package.json verification passed — ready for merge
- prisma.config.ts found at
generator-prisma-client/react-router-starter-cloudflare-workerd/prisma.config.ts, containingschema: './prisma/schema.prisma'- No top-level
prismakey present ingenerator-prisma-client/react-router-starter-cloudflare-workerd/package.jsonPrisma dependencies (
@prisma/adapter-pgand@prisma/clientbumped to 6.14.0) are correctly aligned and the package is clean.
generator-prisma-client/basic-typedsql/prisma/migrations/20250820114100_init/migration.sql
Show resolved
Hide resolved
generator-prisma-client/react-router-starter-cloudflare-workerd/worker-configuration.d.ts
Show resolved
Hide resolved
generator-prisma-client/react-router-starter-cloudflare-workerd/worker-configuration.d.ts
Show resolved
Hide resolved
generator-prisma-client/react-router-starter-cloudflare-workerd/worker-configuration.d.ts
Show resolved
Hide resolved
generator-prisma-client/nextjs-starter-webpack-with-middleware/README.md
Show resolved
Hide resolved
|
FYI, I can still reproduce #8280 with this branch: |
I see you're getting an ECONNREFUSED error, which means you're using wrong database credentials. |
generator-prisma-client/react-router-starter-cloudflare-workerd/README.md
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
generator-prisma-client/basic-typedsql/README.md (1)
40-46: Fix table names: replace “Post” with “TrackingEvent”.Migration in this PR defines
UserandTrackingEvent(notPost). The README should match the schema/migration to avoid confusion.Apply:
-Run the following command to create your SQLite database file. This also creates the `User` and `Post` tables that are defined in [`prisma/schema.prisma`](./prisma/schema.prisma): +Run the following command to create your SQLite database file. This also creates the `User` and `TrackingEvent` tables that are defined in [`prisma/schema.prisma`](./prisma/schema.prisma):
♻️ Duplicate comments (2)
generator-prisma-client/basic-typedsql/README.md (1)
65-65: Link fix looks correct (./src/index.ts) — resolved.This addresses the earlier comment about the incorrect
./index.tspath in the “Run the example” section. Thanks for fixing it.generator-prisma-client/deno-deploy/deno.jsonc (1)
18-25: Resolved: removed hard-coded Deploy project IDThe previously hard-coded Deno Deploy project UUID is no longer present. This prevents accidental linkage to a real project. LGTM.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (7)
generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/client.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/commonInputTypes.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/enums.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/internal/class.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/internal/prismaNamespace.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/models.tsis excluded by!**/generated/**generator-prisma-client/nextjs-starter-webpack-monorepo/packages/prisma/src/generated/prisma/models/Quotes.tsis excluded by!**/generated/**
📒 Files selected for processing (2)
generator-prisma-client/basic-typedsql/README.md(1 hunks)generator-prisma-client/deno-deploy/deno.jsonc(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: FGoessler
PR: prisma/prisma-examples#8260
File: generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json:13-13
Timestamp: 2025-08-22T12:12:24.563Z
Learning: When analyzing changes from package.json seed scripts to "prisma db seed", always verify the actual content of prisma.config.ts rather than relying solely on regex patterns, as the configuration may be properly defined but in a format that doesn't match overly restrictive search patterns.
📚 Learning: 2025-08-22T12:12:24.563Z
Learnt from: FGoessler
PR: prisma/prisma-examples#8260
File: generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json:13-13
Timestamp: 2025-08-22T12:12:24.563Z
Learning: When analyzing changes from package.json seed scripts to "prisma db seed", always verify the actual content of prisma.config.ts rather than relying solely on regex patterns, as the configuration may be properly defined but in a format that doesn't match overly restrictive search patterns.
Applied to files:
generator-prisma-client/basic-typedsql/README.md
🪛 LanguageTool
generator-prisma-client/basic-typedsql/README.md
[grammar] ~65-~65: Use correct spacing
Context: ...l) and print the results to the console. ## Project Structure This example project ...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (27)
- GitHub Check: test (orm/express)
- GitHub Check: test (orm/ai-sdk-nextjs)
- GitHub Check: test (orm/fastify)
- GitHub Check: test (orm/fastify-graphql-sdl-first)
- GitHub Check: test (orm/astro)
- GitHub Check: test (orm/graphql)
- GitHub Check: test (orm/hapi-graphql)
- GitHub Check: test (orm/clerk-nextjs)
- GitHub Check: test (orm/authjs-nextjs)
- GitHub Check: test (orm/fastify-graphql)
- GitHub Check: test (orm/betterauth-nextjs)
- GitHub Check: test (orm/graphql-subscriptions)
- GitHub Check: test (orm/graphql-sdl-first)
- GitHub Check: test (orm/hapi)
- GitHub Check: test (orm/koa)
- GitHub Check: test (orm/nest-graphql)
- GitHub Check: test (orm/nextjs)
- GitHub Check: test (orm/graphql-nexus)
- GitHub Check: test (orm/hapi-graphql-sdl-first)
- GitHub Check: test (orm/grpc)
- GitHub Check: test (orm/nest)
- GitHub Check: test (orm/nest-graphql-sdl-first)
- GitHub Check: test (orm/nuxt)
- GitHub Check: test (orm/nextjs-graphql)
- GitHub Check: test (orm/react-router-7)
- GitHub Check: test (orm/sveltekit)
- GitHub Check: test (orm/solid-start)
🔇 Additional comments (3)
generator-prisma-client/basic-typedsql/README.md (3)
65-67: Minor wording/spacing nit.Consider removing any double spaces around the “## Project Structure” heading to satisfy markdown/grammar linters.
-This command will run [`src/index.ts`](./src/index.ts), which will execute the SQL query defined in [`prisma/sql/conversionByVariant.sql`](./prisma/sql/conversionByVariant.sql) and print the results to the console. - -## Project Structure +This command will run [`src/index.ts`](./src/index.ts), which will execute the SQL query defined in [`prisma/sql/conversionByVariant.sql`](./prisma/sql/conversionByVariant.sql) and print the results to the console. + +## Project Structure⛔ Skipped due to learnings
Learnt from: FGoessler PR: prisma/prisma-examples#8260 File: generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json:13-13 Timestamp: 2025-08-22T12:12:24.563Z Learning: When analyzing changes from package.json seed scripts to "prisma db seed", always verify the actual content of prisma.config.ts rather than relying solely on regex patterns, as the configuration may be properly defined but in a format that doesn't match overly restrictive search patterns.
62-63: Verified:devscript is correctly defined
Thedevscript ingenerator-prisma-client/basic-typedsql/package.jsonexists and invokes your entry point as expected:
- generator-prisma-client/basic-typedsql/package.json, line 8:
"dev": "tsx src/index.ts --watch"No further changes needed.
46-46: Seeding configuration is correctly defined in prisma.config.ts
Theprisma.config.tsfile includes amigrations.seedentry pointing totsx ./prisma/seed.ts, and theprisma/seed.tsfile exists in the example. The README’s description of automatic seeding onpnpm prisma migrate devis accurate—no changes needed.
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
generator-prisma-client/nextjs-starter-webpack-with-middleware/prisma/schema.prisma (1)
17-21: AdddriverAdaptersto edge generator and document Vercel Postgres env mapping
- In
prisma/schema.prisma, thegenerator edgeblock is missingpreviewFeatures, so driver adapters (and extensions likewithAccelerate) won’t be enabled for the Edge client.- In
.env.examplethe template usesDATABASE_URL/DIRECT_URL, but Vercel Postgres suppliesPOSTGRES_PRISMA_URLandPOSTGRES_URL_NON_POOLINGby default—add guidance in the README or schema comments to map those toDATABASE_URL/DIRECT_URLor update thedatasourceaccordingly.Update snippet in
prisma/schema.prisma:generator edge { provider = "prisma-client" output = "../lib/generated/prisma-edge" runtime = "vercel" + previewFeatures = ["driverAdapters", "queryCompiler"] }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
generator-prisma-client/nextjs-starter-webpack-with-middleware/prisma/schema.prisma(2 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: FGoessler
PR: prisma/prisma-examples#8260
File: generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json:13-13
Timestamp: 2025-08-22T12:12:24.563Z
Learning: When analyzing changes from package.json seed scripts to "prisma db seed", always verify the actual content of prisma.config.ts rather than relying solely on regex patterns, as the configuration may be properly defined but in a format that doesn't match overly restrictive search patterns.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (27)
- GitHub Check: test (orm/betterauth-nextjs)
- GitHub Check: test (orm/astro)
- GitHub Check: test (orm/grpc)
- GitHub Check: test (orm/ai-sdk-nextjs)
- GitHub Check: test (orm/clerk-nextjs)
- GitHub Check: test (orm/graphql-auth)
- GitHub Check: test (orm/fastify)
- GitHub Check: test (orm/graphql)
- GitHub Check: test (orm/express)
- GitHub Check: test (orm/fastify-graphql-sdl-first)
- GitHub Check: test (orm/hapi-graphql)
- GitHub Check: test (orm/fastify-graphql)
- GitHub Check: test (orm/hapi-graphql-sdl-first)
- GitHub Check: test (orm/authjs-nextjs)
- GitHub Check: test (orm/graphql-sdl-first)
- GitHub Check: test (orm/graphql-nexus)
- GitHub Check: test (orm/graphql-subscriptions)
- GitHub Check: test (orm/nest)
- GitHub Check: test (orm/hapi)
- GitHub Check: test (orm/nuxt)
- GitHub Check: test (orm/nest-graphql)
- GitHub Check: test (orm/nest-graphql-sdl-first)
- GitHub Check: test (orm/solid-start)
- GitHub Check: test (orm/nextjs)
- GitHub Check: test (orm/koa)
- GitHub Check: test (orm/nextjs-graphql)
- GitHub Check: test (orm/sveltekit)
🔇 Additional comments (2)
generator-prisma-client/nextjs-starter-webpack-with-middleware/prisma/schema.prisma (2)
28-33: Model changes are purely formatting; semantics unchanged
id @default(autoincrement())andcreatedAt @default(now())remain intact; no functional differences. LGTM.
11-15: AddpreviewFeaturesto the Edge generator and verify client outputsThe
edgegenerator ingenerator-prisma-client/nextjs-starter-webpack-with-middleware/prisma/schema.prismacorrectly usesruntime = "vercel"(an alias ofedge-light), but it’s missing the samepreviewFeaturesflags you’ve enabled on the primaryclientgenerator. To ensure the Rust-free client and Driver Adapters work on Edge, add:generator edge { provider = "prisma-client" output = "../lib/generated/prisma-edge" runtime = "vercel" + previewFeatures = ["driverAdapters", "queryCompiler"] }• File: generator-prisma-client/nextjs-starter-webpack-with-middleware/prisma/schema.prisma
• Lines: 11–15After merging, please run
prisma generateand confirm that both output folders are populated:
../lib/generated/prisma../lib/generated/prisma-edge— ensure no errors occur and both clients are generated.
generator-prisma-client/nextjs-starter-webpack-with-middleware/prisma/schema.prisma
Show resolved
Hide resolved
4 participants
This PR:
generator-prisma-clientexamplesprisma@6.14.0, which contains the fixes from feat(client-generator-ts): use base64 encoding on Wasm files loaded by Node.js prisma#27795package.json#prismawithprisma.config.tsSummary by CodeRabbit
Documentation
Bug Fixes
Chores