Update fullstack examples with prisma config and pg adapter

[AmanVarshney01]

Summary by CodeRabbit

• Chores
  • Updated Prisma dependencies to version 6.19.0 and migrated database adapter configuration across multiple projects for improved database connectivity setup.
  • Updated project documentation with revised environment configuration guidance for DATABASE_URL connection strings.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Migrates multiple ORM example projects from Prisma Accelerate extension to Prisma Postgres adapter (PrismaPg), updates Prisma versions to 6.19.0, introduces explicit prisma.config.ts configuration files, adds dotenv devDependency, removes deprecated seed configurations, and updates documentation.

Changes

Cohort / File(s)	Summary
Dependency Updates orm/betterauth-nextjs/package.json, orm/nextjs/package.json, orm/nuxt-prisma-module/package.json, orm/nuxt/package.json, orm/react-router-7/package.json, orm/solid-start/package.json	Replaced @prisma/extension-accelerate with @prisma/adapter-pg (^6.19.0), updated @prisma/client to ^6.19.0, bumped prisma from 6.18.0 to 6.19.0, added dotenv ^17.2.1 as devDependency. Removed Prisma seed configuration blocks.
Prisma Client Initialization orm/betterauth-nextjs/src/lib/prisma.ts, orm/nextjs/lib/prisma.ts, orm/nuxt-prisma-module/lib/prisma.ts, orm/nuxt/prisma/db.ts, orm/react-router-7/app/lib/prisma.ts, orm/solid-start/lib/prisma.ts	Replaced PrismaClient().$extends(withAccelerate()) with adapter-based initialization: const pool = new PrismaPg({ connectionString: process.env.DATABASE_URL! }) followed by new PrismaClient({ adapter: pool }). Removed withAccelerate import, added PrismaPg import.
Prisma Configuration Files orm/betterauth-nextjs/prisma.config.ts, orm/nextjs/prisma.config.ts, orm/nuxt-prisma-module/prisma.config.ts, orm/nuxt/prisma.config.ts, orm/react-router-7/prisma.config.ts, orm/solid-start/prisma.config.ts	Added new prisma.config.ts files with defineConfig export specifying schema path, migrations directory, classic engine, and datasource URL from environment via env('DATABASE_URL').
Seed Files orm/nextjs/prisma/seed.ts, orm/nuxt/prisma/seed.ts	Updated to use PrismaPg adapter instead of default client construction: initialize pool = new PrismaPg(...) and pass to new PrismaClient({ adapter: pool }).
Documentation orm/nextjs/README.md, orm/nuxt-prisma-module/README.md, orm/nuxt/README.md	Updated database URL examples from Prisma Accelerate URLs to standard PostgreSQL connection strings, replaced Accelerate extension workflow with @prisma/adapter-pg setup instructions, updated code examples to reflect PrismaPg pool initialization.
Schema Cleanup orm/betterauth-nextjs/prisma/schema.prisma, orm/nextjs/prisma/schema.prisma, orm/react-router-7/prisma/schema.prisma, orm/solid-start/prisma/schema.prisma	Removed comment lines referencing Prisma Accelerate initialization.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Repetitive changes across six projects: Same migration pattern applied consistently (reduces review complexity despite file count)
• Adapter initialization pattern: Verify PrismaPg pool creation and connection string handling are consistent across all files
• Documentation accuracy: Confirm README updates correctly reflect the new adapter-based setup and environment variable usage
• Configuration files: Ensure prisma.config.ts definitions match across projects and properly reference environment variables

Possibly related PRs

• feat(generator-prisma-client): add nuxt4-starter-nodejs example #8289: Direct adapter migration pattern—replaces Accelerate extension with PrismaPg adapter initialization in Prisma client setup
• Update misc examples #8328: Related Prisma setup refactor—swaps @prisma/extension-accelerate for @prisma/adapter-pg and updates version dependencies
• fix(generator-prisma-client): bump Prisma version, introduce prisma.config.ts #8260: Parallel migration—adds prisma.config.ts files and migrates from Accelerate extension to adapter-pg across example projects

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: adding Prisma configuration files and replacing the Prisma Accelerate extension with the pg adapter across fullstack examples.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

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 (2)

orm/nuxt/README.md (1)

208-226: Remove stale Accelerate removal instructions.

This section still tells readers to uninstall @prisma/extension-accelerate and drop withAccelerate(), but the example now ships with @prisma/adapter-pg. Following these outdated steps won’t help anyone switching databases off Postgres—they actually need guidance on removing or replacing the adapter-based client setup. Please update this block to reflect the new adapter workflow so the migration instructions remain correct.

orm/nextjs/README.md (1)

200-281: Add guidance on removing the Postgres adapter when changing databases.

The new setup initializes PrismaClient with @prisma/adapter-pg, yet this section now says you can target SQLite/MySQL/etc. by only changing the datasource connection. If readers keep the Postgres adapter in place, those drivers won’t work and the example fails. Please update these database-switch instructions to explain how to drop (or replace) the adapter when moving away from Postgres so the steps are actually runnable.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 37abebc and db290c2.

📒 Files selected for processing (26)

• .github/get-ppg-dev/index.js (1 hunks)
• orm/betterauth-nextjs/package.json (1 hunks)
• orm/betterauth-nextjs/prisma.config.ts (1 hunks)
• orm/betterauth-nextjs/prisma/schema.prisma (0 hunks)
• orm/betterauth-nextjs/src/lib/prisma.ts (1 hunks)
• orm/nextjs/README.md (3 hunks)
• orm/nextjs/lib/prisma.ts (1 hunks)
• orm/nextjs/package.json (1 hunks)
• orm/nextjs/prisma.config.ts (1 hunks)
• orm/nextjs/prisma/schema.prisma (0 hunks)
• orm/nuxt-prisma-module/README.md (2 hunks)
• orm/nuxt-prisma-module/lib/prisma.ts (1 hunks)
• orm/nuxt-prisma-module/package.json (1 hunks)
• orm/nuxt-prisma-module/prisma.config.ts (1 hunks)
• orm/nuxt/README.md (2 hunks)
• orm/nuxt/package.json (1 hunks)
• orm/nuxt/prisma.config.ts (1 hunks)
• orm/nuxt/prisma/db.ts (1 hunks)
• orm/react-router-7/app/lib/prisma.ts (1 hunks)
• orm/react-router-7/package.json (2 hunks)
• orm/react-router-7/prisma.config.ts (1 hunks)
• orm/react-router-7/prisma/schema.prisma (0 hunks)
• orm/solid-start/lib/prisma.ts (1 hunks)
• orm/solid-start/package.json (2 hunks)
• orm/solid-start/prisma.config.ts (1 hunks)
• orm/solid-start/prisma/schema.prisma (0 hunks)

💤 Files with no reviewable changes (4)

• orm/solid-start/prisma/schema.prisma
• orm/betterauth-nextjs/prisma/schema.prisma
• orm/react-router-7/prisma/schema.prisma
• orm/nextjs/prisma/schema.prisma

🧰 Additional context used

🧠 Learnings (9)

📓 Common learnings

Learnt from: aidankmcalister
Repo: prisma/prisma-examples PR: 8334
File: orm/fastify-graphql-sdl-first/src/context.ts:1-1
Timestamp: 2025-10-27T13:18:46.546Z
Learning: The prisma/prisma-examples repository is a monorepo containing many independent example projects. When reviewing PRs in this repository, focus only on the files actually changed by the author in that specific PR, not on other example projects or infrastructure that wasn't modified.

Learnt from: aidankmcalister
Repo: prisma/prisma-examples PR: 8334
File: orm/betterauth-astro/src/pages/sign-up/index.astro:20-36
Timestamp: 2025-10-24T17:50:48.569Z
Learning: Do not suggest code changes or improvements to code in Prisma example repositories (prisma/prisma-examples). These examples are carefully set up and intentionally aligned with external documentation and information.

Learnt from: FGoessler
Repo: prisma/prisma-examples PR: 8260
File: generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json:13-13
Timestamp: 2025-08-22T12:12:24.602Z
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.602Z

Learnt from: FGoessler
Repo: prisma/prisma-examples PR: 8260
File: generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json:13-13
Timestamp: 2025-08-22T12:12:24.602Z
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:

• orm/react-router-7/package.json
• orm/betterauth-nextjs/package.json
• orm/solid-start/prisma.config.ts
• orm/betterauth-nextjs/prisma.config.ts
• orm/nuxt/prisma/db.ts
• orm/nextjs/package.json
• .github/get-ppg-dev/index.js
• orm/nuxt-prisma-module/package.json
• orm/nuxt/prisma.config.ts
• orm/betterauth-nextjs/src/lib/prisma.ts
• orm/nuxt-prisma-module/prisma.config.ts
• orm/nuxt-prisma-module/lib/prisma.ts
• orm/nextjs/prisma.config.ts
• orm/react-router-7/prisma.config.ts
• orm/nuxt/package.json
• orm/nuxt/README.md
• orm/solid-start/package.json
• orm/react-router-7/app/lib/prisma.ts
• orm/nextjs/README.md
• orm/nextjs/lib/prisma.ts
• orm/solid-start/lib/prisma.ts
• orm/nuxt-prisma-module/README.md

📚 Learning: 2025-10-15T13:58:59.096Z

Learnt from: AmanVarshney01
Repo: prisma/prisma-examples PR: 8327
File: orm/graphql-auth/prisma/schema.prisma:2-4
Timestamp: 2025-10-15T13:58:59.096Z
Learning: The "prisma-client" generator provider (introduced in Prisma v6) is the newer, ESM-ready alternative to "prisma-client-js". It requires an explicit output path and is better suited for modern runtimes, edge deployments, and will become the default in Prisma v7. Use "prisma-client" for new projects or when modernizing existing projects.

Applied to files:

• orm/react-router-7/package.json
• orm/solid-start/prisma.config.ts
• orm/betterauth-nextjs/prisma.config.ts
• orm/nuxt/prisma/db.ts
• orm/nextjs/package.json
• orm/nuxt-prisma-module/package.json
• orm/nuxt/prisma.config.ts
• orm/betterauth-nextjs/src/lib/prisma.ts
• orm/nuxt-prisma-module/prisma.config.ts
• orm/nuxt-prisma-module/lib/prisma.ts
• orm/nextjs/prisma.config.ts
• orm/react-router-7/prisma.config.ts
• orm/nuxt/package.json
• orm/nuxt/README.md
• orm/solid-start/package.json
• orm/react-router-7/app/lib/prisma.ts
• orm/nextjs/README.md
• orm/nextjs/lib/prisma.ts
• orm/solid-start/lib/prisma.ts
• orm/nuxt-prisma-module/README.md

📚 Learning: 2025-10-15T13:58:29.130Z

Learnt from: AmanVarshney01
Repo: prisma/prisma-examples PR: 8327
File: orm/fastify-graphql/prisma/schema.prisma:2-4
Timestamp: 2025-10-15T13:58:29.130Z
Learning: In Prisma v6.15 and later, `provider = "prisma-client"` is a valid generator configuration value when combined with `engineType = "client"`. This configuration generates a Prisma client without Rust engine binaries, relying on JavaScript driver adapters instead, and is different from the traditional `provider = "prisma-client-js"` configuration.

Applied to files:

• orm/solid-start/prisma.config.ts
• orm/betterauth-nextjs/prisma.config.ts
• orm/nuxt/prisma/db.ts
• orm/nuxt/prisma.config.ts
• orm/betterauth-nextjs/src/lib/prisma.ts
• orm/nuxt-prisma-module/prisma.config.ts
• orm/nuxt-prisma-module/lib/prisma.ts
• orm/nextjs/prisma.config.ts
• orm/react-router-7/prisma.config.ts
• orm/nuxt/README.md
• orm/react-router-7/app/lib/prisma.ts
• orm/nextjs/README.md
• orm/nextjs/lib/prisma.ts
• orm/solid-start/lib/prisma.ts
• orm/nuxt-prisma-module/README.md

📚 Learning: 2025-10-15T13:56:01.807Z

Learnt from: AmanVarshney01
Repo: prisma/prisma-examples PR: 8327
File: orm/graphql-subscriptions/prisma/schema.prisma:1-5
Timestamp: 2025-10-15T13:56:01.807Z
Learning: In Prisma v6.15 and later, `engineType = "client"` is a valid generator configuration value that generates a Prisma client without Rust engine binaries, relying on JavaScript driver adapters instead (e.g., prisma/adapter-pg). This is useful for edge and serverless deployments.

Applied to files:

• orm/nuxt/prisma/db.ts
• orm/betterauth-nextjs/src/lib/prisma.ts
• orm/nuxt-prisma-module/lib/prisma.ts
• orm/nuxt/README.md
• orm/react-router-7/app/lib/prisma.ts
• orm/nextjs/README.md
• orm/nextjs/lib/prisma.ts
• orm/solid-start/lib/prisma.ts
• orm/nuxt-prisma-module/README.md

📚 Learning: 2025-08-22T12:12:43.161Z

Learnt from: FGoessler
Repo: prisma/prisma-examples PR: 8260
File: generator-prisma-client/nextjs-starter-turbopack/components/quotes.tsx:1-1
Timestamp: 2025-08-22T12:12:43.161Z
Learning: In Next.js applications using Prisma, the connection() function from 'next/server' serves a different purpose than 'export const dynamic = force-dynamic'. The connection() function ensures proper database connection context and request isolation, while dynamic = 'force-dynamic' only controls rendering strategy. Both should be used together and are not redundant.

Applied to files:

• orm/nuxt/prisma/db.ts
• .github/get-ppg-dev/index.js
• orm/betterauth-nextjs/src/lib/prisma.ts
• orm/nuxt-prisma-module/lib/prisma.ts
• orm/react-router-7/app/lib/prisma.ts
• orm/nextjs/README.md
• orm/nextjs/lib/prisma.ts
• orm/solid-start/lib/prisma.ts
• orm/nuxt-prisma-module/README.md

📚 Learning: 2025-10-27T13:18:46.546Z

Learnt from: aidankmcalister
Repo: prisma/prisma-examples PR: 8334
File: orm/fastify-graphql-sdl-first/src/context.ts:1-1
Timestamp: 2025-10-27T13:18:46.546Z
Learning: In the prisma/prisma-examples repository, generated Prisma client files (typically at paths like `prisma/generated/client`) are intentionally not committed to the repository. These files are generated at build/test time. Do not flag missing generated client artifacts as issues in reviews.

Applied to files:

• orm/react-router-7/prisma.config.ts
• orm/nuxt/README.md
• orm/nextjs/README.md
• orm/nuxt-prisma-module/README.md

📚 Learning: 2025-10-27T13:18:46.546Z

Learnt from: aidankmcalister
Repo: prisma/prisma-examples PR: 8334
File: orm/fastify-graphql-sdl-first/src/context.ts:1-1
Timestamp: 2025-10-27T13:18:46.546Z
Learning: The prisma/prisma-examples repository is a monorepo containing many independent example projects. When reviewing PRs in this repository, focus only on the files actually changed by the author in that specific PR, not on other example projects or infrastructure that wasn't modified.

Applied to files:

• orm/react-router-7/prisma.config.ts
• orm/nuxt/README.md
• orm/nuxt-prisma-module/README.md

📚 Learning: 2025-10-24T17:50:48.569Z

Learnt from: aidankmcalister
Repo: prisma/prisma-examples PR: 8334
File: orm/betterauth-astro/src/pages/sign-up/index.astro:20-36
Timestamp: 2025-10-24T17:50:48.569Z
Learning: Do not suggest code changes or improvements to code in Prisma example repositories (prisma/prisma-examples). These examples are carefully set up and intentionally aligned with external documentation and information.

Applied to files:

• orm/nuxt/README.md
• orm/nextjs/README.md
• orm/nuxt-prisma-module/README.md

🧬 Code graph analysis (4)

orm/betterauth-nextjs/src/lib/prisma.ts (1)

orm/nuxt/prisma/db.ts (1)

• prisma (16-16)

orm/react-router-7/app/lib/prisma.ts (1)

orm/nuxt/prisma/db.ts (1)

• prisma (16-16)

orm/nextjs/lib/prisma.ts (4)

orm/nuxt/prisma/db.ts (1)

• prisma (16-16)

orm/graphql/src/db.ts (1)

• prisma (4-4)

orm/prisma-mocking-javascript/client.js (1)

• prisma (3-3)

orm/testing-express/src/app.ts (1)

• prisma (5-5)

orm/solid-start/lib/prisma.ts (1)

orm/nuxt/prisma/db.ts (1)

• prisma (16-16)

⏰ 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). (33)

• GitHub Check: test (orm/betterauth-nextjs)
• GitHub Check: test (orm/ai-sdk-nextjs)
• GitHub Check: test (orm/graphql)
• GitHub Check: test (orm/betterauth-astro)
• GitHub Check: test (orm/astro)
• GitHub Check: test (orm/authjs-nextjs)
• GitHub Check: test (orm/clerk-nextjs)
• GitHub Check: test (orm/fastify-graphql)
• GitHub Check: test (orm/fastify)
• GitHub Check: test (orm/fastify-graphql-sdl-first)
• GitHub Check: test (orm/express)
• GitHub Check: test (orm/graphql-nexus)
• GitHub Check: test (orm/graphql-auth)
• GitHub Check: test (orm/graphql-subscriptions)
• GitHub Check: test (orm/graphql-sdl-first)
• GitHub Check: test (orm/grpc)
• GitHub Check: test (orm/hapi-graphql-sdl-first)
• GitHub Check: test (orm/hapi-graphql)
• GitHub Check: test (orm/hapi)
• GitHub Check: test (orm/nest)
• GitHub Check: test (orm/hono)
• GitHub Check: test (orm/nest-graphql)
• GitHub Check: test (orm/nextjs)
• GitHub Check: test (orm/koa)
• GitHub Check: test (orm/nextjs-graphql)
• GitHub Check: test (orm/nest-graphql-sdl-first)
• GitHub Check: test (orm/nextjs-trpc)
• GitHub Check: test (orm/nuxt)
• GitHub Check: test (orm/script)
• GitHub Check: test (orm/sveltekit)
• GitHub Check: test (orm/solid-start)
• GitHub Check: test (orm/react-router-7)
• GitHub Check: test (orm/testing-express)

🔇 Additional comments (12)

orm/nuxt/prisma/db.ts (3)

2-2: LGTM!

Correct import for the PostgreSQL adapter migration.

---

6-7: LGTM! Correct migration to adapter-based pattern.

The migration from Prisma Accelerate extension to the PostgreSQL adapter is correctly implemented. The pool is properly initialized with the database connection string and passed to PrismaClient.

---

1-1: Update comment URL to reference Nuxt or generic Prisma best practices.

The comment references Next.js-specific documentation, but this is a Nuxt example. This inconsistency could confuse users.

Consider updating to a Nuxt-specific or framework-agnostic Prisma guide.

⛔ Skipped due to learnings

Learnt from: FGoessler
Repo: prisma/prisma-examples PR: 8260
File: generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json:13-13
Timestamp: 2025-08-22T12:12:24.602Z
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.

Learnt from: aidankmcalister
Repo: prisma/prisma-examples PR: 8334
File: orm/betterauth-astro/src/pages/sign-up/index.astro:20-36
Timestamp: 2025-10-24T17:50:48.569Z
Learning: Do not suggest code changes or improvements to code in Prisma example repositories (prisma/prisma-examples). These examples are carefully set up and intentionally aligned with external documentation and information.

Learnt from: aidankmcalister
Repo: prisma/prisma-examples PR: 8334
File: orm/fastify-graphql-sdl-first/src/context.ts:1-1
Timestamp: 2025-10-27T13:18:46.546Z
Learning: In the prisma/prisma-examples repository, generated Prisma client files (typically at paths like `prisma/generated/client`) are intentionally not committed to the repository. These files are generated at build/test time. Do not flag missing generated client artifacts as issues in reviews.

Learnt from: FGoessler
Repo: prisma/prisma-examples PR: 8260
File: generator-prisma-client/nextjs-starter-turbopack/components/quotes.tsx:1-1
Timestamp: 2025-08-22T12:12:43.161Z
Learning: In Next.js applications using Prisma, the connection() function from 'next/server' serves a different purpose than 'export const dynamic = force-dynamic'. The connection() function ensures proper database connection context and request isolation, while dynamic = 'force-dynamic' only controls rendering strategy. Both should be used together and are not redundant.

Learnt from: AmanVarshney01
Repo: prisma/prisma-examples PR: 8327
File: orm/graphql-auth/prisma/schema.prisma:2-4
Timestamp: 2025-10-15T13:58:59.096Z
Learning: The "prisma-client" generator provider (introduced in Prisma v6) is the newer, ESM-ready alternative to "prisma-client-js". It requires an explicit output path and is better suited for modern runtimes, edge deployments, and will become the default in Prisma v7. Use "prisma-client" for new projects or when modernizing existing projects.

.github/get-ppg-dev/index.js (1)

15-15: Verify the property exists and add defensive error handling.

The property path change from server.ppg.url to server.database.prismaORMConnectionString is part of the adapter migration and is integrated into the CI test pipeline. However:

1. Since unstable_startServer is an undocumented unstable API, the exact object structure is not publicly documented and could change without notice
2. The downstream CI script in .github/tests/databases/prisma-postgres/run.sh waits for output matching ^prisma+postgres:// and fails with a timeout if this pattern isn't found within 60 seconds
3. If server.database.prismaORMConnectionString is undefined, the console output will be "undefined", causing the test to fail

Before merging, verify:

• The tests actually pass with the current @prisma/dev version
• Consider adding defensive checks (e.g., console.log(server.database?.prismaORMConnectionString || '')) to catch potential undefined values and provide clearer error messages

orm/nuxt-prisma-module/README.md (1)

45-45: Documentation accurately reflects the adapter-pg migration.

The README correctly updates the DATABASE_URL format from Prisma Accelerate to a standard PostgreSQL connection string and documents the new @prisma/adapter-pg usage pattern with clear code examples.

Also applies to: 70-78

orm/react-router-7/prisma.config.ts (1)

1-13: Clean Prisma configuration setup.

The configuration correctly uses defineConfig with appropriate paths, the classic engine, and environment-based datasource URL. The dotenv import ensures environment variables are loaded before configuration is processed.

orm/solid-start/lib/prisma.ts (1)

1-7: Proper migration to PrismaPg adapter.

The implementation correctly replaces the extension-based approach with the adapter pool pattern. The PrismaPg pool is initialized with the connection string and passed to PrismaClient via the adapter option, maintaining the same export interface.

orm/betterauth-nextjs/prisma.config.ts (1)

1-13: Configuration correctly structured.

The Prisma configuration properly defines all required fields with appropriate paths and the classic engine. The dotenv import ensures DATABASE_URL is available during configuration.

orm/solid-start/prisma.config.ts (1)

1-14: Configuration includes seed script definition.

The configuration correctly includes the seed script within the migrations block (line 8), eliminating the need for a separate package.json seed script entry. All other fields are properly configured.

orm/react-router-7/app/lib/prisma.ts (1)

1-11: Adapter migration with proper singleton pattern.

The migration to PrismaPg adapter is correctly implemented, and the global singleton pattern for development (lines 7-9) ensures proper connection reuse during hot module replacement.

orm/betterauth-nextjs/src/lib/prisma.ts (1)

1-11: Clean adapter integration with development safeguards.

The PrismaPg adapter implementation is correct, and the development-mode singleton pattern (lines 7-9) prevents connection pool exhaustion during hot reloads.

orm/react-router-7/package.json (1)

13-13: Dependencies correctly updated for adapter-pg migration.

The package correctly replaces @prisma/extension-accelerate with @prisma/adapter-pg (line 13) and adds dotenv as a devDependency (line 27) to support environment variable loading in the new configuration pattern.

Also applies to: 27-27

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between db290c2 and 805b08a.

📒 Files selected for processing (6)

• .github/get-ppg-dev/index.js (1 hunks)
• .github/tests/orm/betterauth-nextjs/run.sh (2 hunks)
• .github/tests/orm/nextjs/run.sh (2 hunks)
• .github/tests/orm/nuxt/run.sh (2 hunks)
• .github/tests/orm/react-router-7/run.sh (2 hunks)
• .github/tests/orm/solid-start/run.sh (2 hunks)

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: aidankmcalister
Repo: prisma/prisma-examples PR: 8334
File: orm/fastify-graphql-sdl-first/src/context.ts:1-1
Timestamp: 2025-10-27T13:18:46.546Z
Learning: The prisma/prisma-examples repository is a monorepo containing many independent example projects. When reviewing PRs in this repository, focus only on the files actually changed by the author in that specific PR, not on other example projects or infrastructure that wasn't modified.

Learnt from: aidankmcalister
Repo: prisma/prisma-examples PR: 8334
File: orm/betterauth-astro/src/pages/sign-up/index.astro:20-36
Timestamp: 2025-10-24T17:50:48.569Z
Learning: Do not suggest code changes or improvements to code in Prisma example repositories (prisma/prisma-examples). These examples are carefully set up and intentionally aligned with external documentation and information.

Learnt from: FGoessler
Repo: prisma/prisma-examples PR: 8260
File: generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json:13-13
Timestamp: 2025-08-22T12:12:24.602Z
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.602Z

Learnt from: FGoessler
Repo: prisma/prisma-examples PR: 8260
File: generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json:13-13
Timestamp: 2025-08-22T12:12:24.602Z
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:

• .github/tests/orm/betterauth-nextjs/run.sh
• .github/tests/orm/nextjs/run.sh
• .github/tests/orm/nuxt/run.sh
• .github/tests/orm/react-router-7/run.sh
• .github/tests/orm/solid-start/run.sh
• .github/get-ppg-dev/index.js

📚 Learning: 2025-08-22T12:12:43.161Z

Learnt from: FGoessler
Repo: prisma/prisma-examples PR: 8260
File: generator-prisma-client/nextjs-starter-turbopack/components/quotes.tsx:1-1
Timestamp: 2025-08-22T12:12:43.161Z
Learning: In Next.js applications using Prisma, the connection() function from 'next/server' serves a different purpose than 'export const dynamic = force-dynamic'. The connection() function ensures proper database connection context and request isolation, while dynamic = 'force-dynamic' only controls rendering strategy. Both should be used together and are not redundant.

Applied to files:

• .github/get-ppg-dev/index.js

⏰ 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). (31)

• GitHub Check: test (orm/astro)
• GitHub Check: test (orm/betterauth-nextjs)
• GitHub Check: test (orm/clerk-nextjs)
• GitHub Check: test (orm/betterauth-astro)
• GitHub Check: test (orm/express)
• GitHub Check: test (orm/ai-sdk-nextjs)
• GitHub Check: test (orm/fastify-graphql-sdl-first)
• GitHub Check: test (orm/hono)
• GitHub Check: test (orm/grpc)
• GitHub Check: test (orm/fastify)
• GitHub Check: test (orm/authjs-nextjs)
• GitHub Check: test (orm/hapi-graphql)
• GitHub Check: test (orm/graphql-auth)
• GitHub Check: test (orm/graphql-subscriptions)
• GitHub Check: test (orm/graphql-sdl-first)
• GitHub Check: test (orm/hapi)
• GitHub Check: test (orm/fastify-graphql)
• GitHub Check: test (orm/graphql)
• GitHub Check: test (orm/koa)
• GitHub Check: test (orm/graphql-nexus)
• GitHub Check: test (orm/nest)
• GitHub Check: test (orm/hapi-graphql-sdl-first)
• GitHub Check: test (orm/nest-graphql-sdl-first)
• GitHub Check: test (orm/nest-graphql)
• GitHub Check: test (orm/nuxt)
• GitHub Check: test (orm/nextjs-graphql)
• GitHub Check: test (orm/nextjs-trpc)
• GitHub Check: test (orm/nextjs)
• GitHub Check: test (orm/react-router-7)
• GitHub Check: test (orm/solid-start)
• GitHub Check: test (orm/sveltekit)

🔇 Additional comments (5)

.github/tests/orm/solid-start/run.sh (1)

38-49: LGTM! Pattern updated correctly for standard PostgreSQL URLs.

The grep pattern change from ^prisma+postgres:// to ^postgres:// correctly aligns with the new adapter-pg workflow where standard PostgreSQL connection strings are emitted.

.github/tests/orm/betterauth-nextjs/run.sh (1)

38-49: LGTM! Consistent pattern update.

The changes correctly update the log parsing to match standard PostgreSQL URLs, consistent with the adapter-pg migration.

.github/tests/orm/react-router-7/run.sh (1)

38-49: LGTM! Test updated for adapter-pg workflow.

The grep pattern correctly matches the standard PostgreSQL URLs now emitted by the dev server.

.github/tests/orm/nuxt/run.sh (1)

38-49: LGTM! Correctly updated for PostgreSQL URL format.

The changes align with the broader migration to adapter-pg across the examples.

.github/tests/orm/nextjs/run.sh (1)

38-49: LGTM! Final test script consistently updated.

All test scripts now correctly parse the standard PostgreSQL connection string format, completing the migration to adapter-pg.