Skip to content

Conversation

@AmanVarshney01
Copy link
Contributor

@AmanVarshney01 AmanVarshney01 commented Oct 31, 2025

Summary by CodeRabbit

Release Notes

  • Chores

    • Removed the Bun + Prisma example project.
    • Updated Prisma and adapter dependencies to version 6.18.0.
  • Refactor

    • Simplified database configuration by consolidating to a single DATABASE_URL environment variable across examples.
    • Updated Prisma generator output paths and added explicit client engine type configuration.

@coderabbitai
Copy link

coderabbitai bot commented Oct 31, 2025

Walkthrough

Multiple example projects in generator-prisma-client are updated to Prisma 6.18.0 with new prisma.config.ts configuration pattern, adapter-pg integration replacing Accelerate, and standardized client generation paths. The bun-with-prisma-driver-adapters example is completely removed.

Changes

Cohort / File(s) Change Summary
Bun with Prisma Driver Adapters - Complete Removal
generator-prisma-client/bun-with-prisma-driver-adapters/.*
Entire example project directory removed, including .env.example, .gitignore, README.md, db.ts, index.ts, package.json, prisma.config.ts, tsconfig.json, and prisma/schema.prisma, prisma/seed.ts files.
Bun Example - Package & Adapter Migration
generator-prisma-client/bun/package.json
Updated Prisma and adapter dependencies from 6.15.0 to ^6.18.0; replaced @prisma/extension-accelerate with @prisma/adapter-pg; removed bun-types devDependency.
Bun Example - Client & Config Updates
generator-prisma-client/bun/db.ts, generator-prisma-client/bun/prisma.config.ts
Updated PrismaClient import path and replaced Accelerate extension with PrismaPg adapter initialization using DATABASE_URL. Added new prisma.config.ts with schema path, migrations, classic engine, and datasource configuration.
Bun Example - Schema & README
generator-prisma-client/bun/prisma/schema.prisma, generator-prisma-client/bun/README.md
Updated generator block: output path changed to ./generated/ and added engineType = "client"; updated README migration command to use bun --bun prisma migrate dev.
Deno Deploy - Package & Environment
generator-prisma-client/deno-deploy/.env.example, generator-prisma-client/deno-deploy/deno.jsonc
Removed DIRECT_URL and DATABASE_URL from .env.example. Updated all Prisma package versions from 6.14.0 to ^6.18.0, including new @prisma/adapter-pg entry.
Deno Deploy - Documentation & Config
generator-prisma-client/deno-deploy/README.md, generator-prisma-client/deno-deploy/prisma.config.ts
Simplified prerequisites to single Prisma Postgres connection string (removed Accelerate reference). Added prisma.config.ts with engine and datasource configuration using DATABASE_URL.
Deno Deploy - Schema & Client Paths
generator-prisma-client/deno-deploy/prisma/schema.prisma, generator-prisma-client/deno-deploy/src/db.ts, generator-prisma-client/deno-deploy/src/prisma-enums.ts
Updated generator output from ../src/generated/prisma to ./generated/ and added engineType = "client". Removed directUrl from datasource. Updated client import paths from ./generated/prisma/* to ../prisma/generated/*.
Deno Deploy - Environment Variable Migration
generator-prisma-client/deno-deploy/prisma/seed.ts, generator-prisma-client/deno-deploy/src/main.ts
Replaced environment variable checks and usage from DIRECT_URL to DATABASE_URL across seed and main entry point files.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

  • File scope: Changes span 3 example projects with 20+ affected files; one entire project removed, two substantially restructured.
  • Pattern consistency: Most changes follow repeatable patterns (version bumps, adapter substitutions, path migrations), reducing per-file review overhead.
  • Logic changes: Adapter switching from Accelerate to @prisma/adapter-pg requires verification of initialization correctness; environment variable consolidation (DIRECT_URLDATABASE_URL) necessitates tracing through dependent code paths.
  • Configuration complexity: Introduction of prisma.config.ts with new defineConfig pattern and engine type specification requires validation against Prisma 6.18.0 expectations.

Areas requiring extra attention:

  • Verification that @prisma/adapter-pg initialization with DATABASE_URL environment variable matches updated Prisma 6.18.0 adapter API.
  • Confirmation that output path changes (./generated/ vs. ../generated/prisma) correctly resolve in both bun and deno-deploy examples.
  • Validation that engineType = "client" in generator blocks is compatible with the declared Prisma versions and runtime targets.
  • Ensure all references to DIRECT_URL are completely migrated to DATABASE_URL across deno-deploy example.

Possibly related PRs

Pre-merge checks

❌ Failed checks (1 warning, 1 inconclusive)
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.
Title Check ❓ Inconclusive The title "Update Bun & Deno examples" is related to the changeset as it correctly identifies which directories are being modified. However, the title lacks specificity about the nature of the changes. The changeset includes significant modifications across both directories—including adapter migrations (from Accelerate to driver adapters in the Bun example), dependency version updates, configuration changes, environment variable refactoring, and the complete removal of the bun-with-prisma-driver-adapters subdirectory. The generic verb "Update" does not clearly convey to a teammate scanning the history what the primary objectives of the PR are or what kind of changes to expect, which falls short of the expectation that the title should be "clear and specific enough that a teammate scanning history understands the primary change." Consider making the title more specific about the primary change. For example, "Migrate Bun examples to driver adapters and update configurations" or "Update Bun and Deno examples with driver adapters and configuration changes" would better communicate the main objectives. This would help reviewers quickly understand the scope and intent of the changes without having to review the full changeset details.
✅ Passed checks (1 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

📜 Recent 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 0b9cd74.

⛔ Files ignored due to path filters (2)
  • generator-prisma-client/bun/bun.lock is excluded by !**/*.lock
  • generator-prisma-client/deno-deploy/deno.lock is excluded by !**/*.lock
📒 Files selected for processing (24)
  • generator-prisma-client/bun-with-prisma-driver-adapters/.env.example (0 hunks)
  • generator-prisma-client/bun-with-prisma-driver-adapters/.gitignore (0 hunks)
  • generator-prisma-client/bun-with-prisma-driver-adapters/README.md (0 hunks)
  • generator-prisma-client/bun-with-prisma-driver-adapters/db.ts (0 hunks)
  • generator-prisma-client/bun-with-prisma-driver-adapters/index.ts (0 hunks)
  • generator-prisma-client/bun-with-prisma-driver-adapters/package.json (0 hunks)
  • generator-prisma-client/bun-with-prisma-driver-adapters/prisma.config.ts (0 hunks)
  • generator-prisma-client/bun-with-prisma-driver-adapters/prisma/schema.prisma (0 hunks)
  • generator-prisma-client/bun-with-prisma-driver-adapters/prisma/seed.ts (0 hunks)
  • generator-prisma-client/bun-with-prisma-driver-adapters/tsconfig.json (0 hunks)
  • generator-prisma-client/bun/README.md (1 hunks)
  • generator-prisma-client/bun/db.ts (1 hunks)
  • generator-prisma-client/bun/package.json (1 hunks)
  • generator-prisma-client/bun/prisma.config.ts (1 hunks)
  • generator-prisma-client/bun/prisma/schema.prisma (1 hunks)
  • generator-prisma-client/deno-deploy/.env.example (0 hunks)
  • generator-prisma-client/deno-deploy/README.md (2 hunks)
  • generator-prisma-client/deno-deploy/deno.jsonc (1 hunks)
  • generator-prisma-client/deno-deploy/prisma.config.ts (2 hunks)
  • generator-prisma-client/deno-deploy/prisma/schema.prisma (2 hunks)
  • generator-prisma-client/deno-deploy/prisma/seed.ts (1 hunks)
  • generator-prisma-client/deno-deploy/src/db.ts (1 hunks)
  • generator-prisma-client/deno-deploy/src/main.ts (1 hunks)
  • generator-prisma-client/deno-deploy/src/prisma-enums.ts (1 hunks)
💤 Files with no reviewable changes (11)
  • generator-prisma-client/bun-with-prisma-driver-adapters/prisma/seed.ts
  • generator-prisma-client/deno-deploy/.env.example
  • generator-prisma-client/bun-with-prisma-driver-adapters/package.json
  • generator-prisma-client/bun-with-prisma-driver-adapters/.env.example
  • generator-prisma-client/bun-with-prisma-driver-adapters/db.ts
  • generator-prisma-client/bun-with-prisma-driver-adapters/prisma/schema.prisma
  • generator-prisma-client/bun-with-prisma-driver-adapters/.gitignore
  • generator-prisma-client/bun-with-prisma-driver-adapters/README.md
  • generator-prisma-client/bun-with-prisma-driver-adapters/tsconfig.json
  • generator-prisma-client/bun-with-prisma-driver-adapters/prisma.config.ts
  • generator-prisma-client/bun-with-prisma-driver-adapters/index.ts
🧰 Additional context used
🧠 Learnings (7)
📓 Common learnings
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: 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: 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.
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.
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.
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.
📚 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:

  • generator-prisma-client/deno-deploy/src/db.ts
  • generator-prisma-client/deno-deploy/src/prisma-enums.ts
  • generator-prisma-client/deno-deploy/README.md
  • generator-prisma-client/bun/README.md
  • generator-prisma-client/deno-deploy/prisma.config.ts
  • generator-prisma-client/deno-deploy/deno.jsonc
  • generator-prisma-client/deno-deploy/prisma/seed.ts
  • generator-prisma-client/bun/prisma/schema.prisma
  • generator-prisma-client/bun/prisma.config.ts
  • generator-prisma-client/bun/db.ts
  • generator-prisma-client/bun/package.json
  • generator-prisma-client/deno-deploy/prisma/schema.prisma
📚 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:

  • generator-prisma-client/deno-deploy/src/db.ts
  • generator-prisma-client/deno-deploy/src/prisma-enums.ts
  • generator-prisma-client/deno-deploy/README.md
  • generator-prisma-client/deno-deploy/deno.jsonc
  • generator-prisma-client/deno-deploy/prisma/seed.ts
  • generator-prisma-client/bun/prisma/schema.prisma
  • generator-prisma-client/bun/prisma.config.ts
  • generator-prisma-client/bun/db.ts
  • generator-prisma-client/bun/package.json
  • generator-prisma-client/deno-deploy/prisma/schema.prisma
📚 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:

  • generator-prisma-client/deno-deploy/src/db.ts
  • generator-prisma-client/deno-deploy/src/prisma-enums.ts
  • generator-prisma-client/deno-deploy/README.md
  • generator-prisma-client/deno-deploy/prisma.config.ts
  • generator-prisma-client/deno-deploy/deno.jsonc
  • generator-prisma-client/deno-deploy/prisma/seed.ts
  • generator-prisma-client/bun/prisma/schema.prisma
  • generator-prisma-client/deno-deploy/src/main.ts
  • generator-prisma-client/bun/prisma.config.ts
  • generator-prisma-client/bun/db.ts
  • generator-prisma-client/bun/package.json
  • generator-prisma-client/deno-deploy/prisma/schema.prisma
📚 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:

  • generator-prisma-client/deno-deploy/src/db.ts
  • generator-prisma-client/deno-deploy/README.md
  • generator-prisma-client/deno-deploy/prisma.config.ts
  • generator-prisma-client/deno-deploy/deno.jsonc
  • generator-prisma-client/deno-deploy/prisma/seed.ts
  • generator-prisma-client/bun/prisma/schema.prisma
  • generator-prisma-client/bun/prisma.config.ts
  • generator-prisma-client/bun/db.ts
  • generator-prisma-client/bun/package.json
  • generator-prisma-client/deno-deploy/prisma/schema.prisma
📚 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:

  • generator-prisma-client/deno-deploy/src/db.ts
  • generator-prisma-client/deno-deploy/README.md
  • generator-prisma-client/deno-deploy/prisma.config.ts
  • generator-prisma-client/deno-deploy/deno.jsonc
  • generator-prisma-client/deno-deploy/prisma/seed.ts
  • generator-prisma-client/bun/prisma/schema.prisma
  • generator-prisma-client/deno-deploy/src/main.ts
  • generator-prisma-client/bun/prisma.config.ts
  • generator-prisma-client/bun/db.ts
  • generator-prisma-client/bun/package.json
  • generator-prisma-client/deno-deploy/prisma/schema.prisma
📚 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:

  • generator-prisma-client/deno-deploy/src/db.ts
  • generator-prisma-client/bun/db.ts
🧬 Code graph analysis (2)
generator-prisma-client/deno-deploy/prisma/seed.ts (1)
generator-prisma-client/deno-deploy/src/db.ts (1)
  • getDb (8-13)
generator-prisma-client/deno-deploy/src/main.ts (1)
generator-prisma-client/deno-deploy/src/db.ts (1)
  • getDb (8-13)
⏰ 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/betterauth-astro)
  • GitHub Check: test (orm/fastify-graphql)
  • GitHub Check: test (orm/ai-sdk-nextjs)
  • GitHub Check: test (orm/astro)
  • GitHub Check: test (orm/betterauth-nextjs)
  • GitHub Check: test (orm/express)
  • GitHub Check: test (orm/graphql-auth)
  • GitHub Check: test (orm/authjs-nextjs)
  • GitHub Check: test (orm/fastify-graphql-sdl-first)
  • GitHub Check: test (orm/clerk-nextjs)
  • GitHub Check: test (orm/fastify)
  • GitHub Check: test (orm/nest-graphql-sdl-first)
  • GitHub Check: test (orm/graphql)
  • GitHub Check: test (orm/graphql-sdl-first)
  • GitHub Check: test (orm/graphql-nexus)
  • GitHub Check: test (orm/hapi-graphql-sdl-first)
  • GitHub Check: test (orm/hapi-graphql)
  • GitHub Check: test (orm/nextjs-graphql)
  • GitHub Check: test (orm/hapi)
  • GitHub Check: test (orm/graphql-subscriptions)
  • GitHub Check: test (orm/hono)
  • GitHub Check: test (orm/grpc)
  • GitHub Check: test (orm/nextjs)
  • GitHub Check: test (orm/nest)
  • GitHub Check: test (orm/nest-graphql)
  • GitHub Check: test (orm/react-router-7)
  • GitHub Check: test (orm/postgis-express)
  • GitHub Check: test (orm/solid-start)
  • GitHub Check: test (orm/nuxt)
  • GitHub Check: test (orm/nextjs-trpc)
  • GitHub Check: test (orm/sveltekit)
🔇 Additional comments (17)
generator-prisma-client/deno-deploy/prisma/seed.ts (1)

6-11: Environment variable migration looks good.

The change from DIRECT_URL to DATABASE_URL is consistent with the broader migration from Prisma Accelerate to direct database connections using adapter-pg. The error message and usage are both correctly updated.

generator-prisma-client/deno-deploy/prisma.config.ts (1)

1-17: Modern Prisma configuration pattern implemented correctly.

The new prisma.config.ts file properly implements Prisma v6's configuration pattern with environment-based datasource configuration. The engine: "classic" setting and seed command configuration align well with the Deno runtime environment.

generator-prisma-client/deno-deploy/deno.jsonc (1)

13-16: Prisma dependencies updated consistently.

All Prisma packages updated together to version ^6.18.0, which is good practice for maintaining compatibility across the Prisma toolchain.

generator-prisma-client/deno-deploy/src/db.ts (1)

2-2: Import path correctly updated.

The PrismaClient import path update aligns with the new generator output location (./generated/ in schema.prisma). The relative path correctly resolves to prisma/generated/client.ts from the src/ directory.

generator-prisma-client/deno-deploy/src/main.ts (1)

9-14: Environment variable migration applied consistently.

The change from DIRECT_URL to DATABASE_URL matches the updates in seed.ts and aligns with the migration from Prisma Accelerate to direct database connections using adapter-pg.

generator-prisma-client/deno-deploy/README.md (2)

9-9: Prerequisites section simplified appropriately.

The updated prerequisites now correctly reflect the simplified setup using a single Prisma Postgres connection string instead of separate Accelerate and direct connection strings.


47-55: Environment setup documentation updated correctly.

The documentation now accurately reflects the use of DATABASE_URL instead of DIRECT_URL, matching the code changes throughout the project.

generator-prisma-client/deno-deploy/src/prisma-enums.ts (1)

1-1: Export path updated consistently.

The re-export path change aligns with the new generator output location, consistent with the update in db.ts.

generator-prisma-client/deno-deploy/prisma/schema.prisma (3)

2-5: Generator configuration updated to Prisma v6 best practices.

The addition of engineType = "client" and the updated output path to ./generated/ are correct for Prisma v6.15+. This configuration generates a Prisma client without Rust engine binaries, relying on JavaScript driver adapters (adapter-pg), which is ideal for Deno Deploy edge deployments.


9-10: Datasource simplified for direct connections.

The removal of directUrl and reliance on a single DATABASE_URL correctly reflects the migration from Prisma Accelerate to direct database connections using adapter-pg.


19-22: Model formatting adjustments look good.

Minor spacing adjustments to field attributes maintain consistency without changing semantics.

generator-prisma-client/bun/README.md (1)

50-50: LGTM!

The --bun flag ensures the Prisma CLI runs in native Bun mode, which aligns with the Bun runtime optimization focus mentioned in the README and the runtime = "bun" configuration in the schema.

generator-prisma-client/bun/package.json (1)

6-13: LGTM!

The Prisma version bump to 6.18.0 and addition of @prisma/adapter-pg and @prisma/client properly support the new adapter-based architecture that replaces the Accelerate extension.

generator-prisma-client/bun/prisma/schema.prisma (1)

4-9: LGTM!

The generator configuration correctly uses the modern prisma-client provider with engineType = "client" for adapter-based deployment. The output path ./generated/ correctly resolves to prisma/generated/, matching the import path in db.ts. Based on learnings.

generator-prisma-client/bun/prisma.config.ts (1)

1-12: LGTM!

The new prisma.config.ts file follows the modern Prisma v6 configuration pattern. The configuration correctly specifies schema location, migrations path, and environment-based datasource URL.

generator-prisma-client/bun/db.ts (2)

1-2: LGTM!

The import path correctly reflects the new generator output location, and the PrismaPg adapter import properly supports the adapter-based architecture that replaces the Accelerate extension.


4-5: LGTM!

The adapter-based PrismaClient initialization correctly uses PrismaPg with the DATABASE_URL connection string, properly replacing the previous Accelerate extension approach. This aligns with the schema's engineType = "client" configuration. Based on learnings.


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

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

Copy link
Contributor

@mhartington mhartington left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few things, but overall good

@AmanVarshney01 AmanVarshney01 changed the base branch from latest to prisma-7 November 7, 2025 11:51
@AmanVarshney01 AmanVarshney01 merged commit fcdff40 into prisma-7 Nov 14, 2025
46 of 47 checks passed
@AmanVarshney01 AmanVarshney01 deleted the dc-5547-prisma-examples-update-bun-deno-examples branch November 14, 2025 04:53
AmanVarshney01 added a commit that referenced this pull request Nov 19, 2025
* Update all accelerate example (#8373)

* Update misc examples (#8372)

* Update misc examples with prisma.config.ts and adapter (#8362)

* Update HTTP web server examples (#8354)

* update all nextjs examples in `generator-prisma-client/` (#8342)

* Update fullstack examples with prisma config and pg adapter (#8344)

Co-authored-by: Nurul Sundarani <sundarani@prisma.io>

* Update Nuxt & React Router examples (#8368)

* Update optimize examples (#8375)

* Update Bun & Deno examples (#8343)

* Update GraphQL examples with prisma.config.ts and pg adapter (#8345)

* update cockroachdb, postgresql-supabase, prisma-postgres examples (#8374)

* remove engine classic and url from schema.prisma

* update deployment

* update readme

* delete all lock files and update prisma version to 7.0.0

* update remaining examples

* update d1 example

* fix

* update turso example

* fix

* update nuxt example

* fix nextjs example

* update all deps to 7.0.0

* fix

---------

Co-authored-by: Nurul Sundarani <sundarani@prisma.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants