Update nuxt guides

[AmanVarshney01]

Summary by CodeRabbit

• Documentation
  • Added a compatibility warning about the Prisma Nuxt module with Prisma ORM 7 and custom generator setups.
  • Rewrote the Nuxt integration guide to show direct Prisma ORM usage with PostgreSQL rather than via the Nuxt module.
  • Updated database setup and examples from SQLite to PostgreSQL.
  • Updated code examples and deployment instructions to match the new direct Prisma/Postgres setup.

[coderabbitai]

Walkthrough

Adds a caution that @prisma/nuxt is unsupported with Prisma ORM 7 or custom generator client { output = ... }, and rewrites the Nuxt guide to use Prisma ORM directly with PostgreSQL, replacing module/Accelerate guidance with a Prisma client singleton, updated schema, seed, migration, and deployment instructions.

Changes

Cohort / File(s)	Summary
Prisma Nuxt warning content/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdx	Adds a cautionary warning that @prisma/nuxt is not supported with Prisma ORM 7 or when using a custom generator client { output = ... }, and directs Prisma 7 users to the general Nuxt guide.
Nuxt guide rewrite (Prisma → Postgres) content/800-guides/100-nuxt.mdx	Full rewrite replacing Nuxt module/Accelerate patterns with direct Prisma ORM usage: switches datasource from SQLite to PostgreSQL, introduces Prisma client singleton and adapter files (e.g., lib/prisma.ts, prisma.config.ts, prisma/seed.ts), updates schema.prisma (provider/output), migration/seed commands, example components to call prisma.user.findFirst(), and deployment/env guidance for DATABASE_URL/Vercel.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20–30 minutes

• Verify internal consistency of code examples (singleton lib/prisma.ts, prisma.config.ts, seed script, and component usage).
• Check schema/provider/output edits and migration commands for accuracy (Postgres vs SQLite, generator output path).
• Confirm the deprecation warning text is accurate and not contradictory with other docs.

Possibly related PRs

• fix: update cloudflare D1 guide #7055 — Related edits to Prisma configuration and adapter initialization in docs (overlaps on prisma.config.ts and adapter patterns).
• Update docs to perform migrations with connection pooling and Prisma config #7266 — Related changes migrating examples from in-schema directUrl to separate prisma.config.ts and updating runtime client wiring (prisma.ts/prisma.config.ts).

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title "Update nuxt guides" is vague and generic, failing to capture the significant architectural shift from the Nuxt module to direct Prisma ORM with PostgreSQL.	Consider a more descriptive title that reflects the main changes, such as "Migrate Nuxt guide from @prisma/nuxt module to direct Prisma ORM with Postgres" or "Rework Nuxt guide to use Prisma ORM with Prisma Postgres instead of Nuxt module".

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 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 7413b69 and e08a3f4.

📒 Files selected for processing (1)

• content/800-guides/100-nuxt.mdx (9 hunks)

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: ankur-arch
Repo: prisma/docs PR: 7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.

📚 Learning: 2025-10-08T16:22:57.129Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.

Applied to files:

• content/800-guides/100-nuxt.mdx

📚 Learning: 2025-10-09T21:32:50.340Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.

Applied to files:

• content/800-guides/100-nuxt.mdx

📚 Learning: 2025-10-08T16:23:00.388Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".

Applied to files:

• content/800-guides/100-nuxt.mdx

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

• GitHub Check: Check internal links
• GitHub Check: Cloudflare Pages

🔇 Additional comments (9)

content/800-guides/100-nuxt.mdx (9)

1-21: Intro section looks good.

The updated title, description, and learning objectives clearly reflect the shift to direct Prisma ORM usage with PostgreSQL. Sentence case and product naming are correct.

---

27-27: Verify Node.js version guidance link targets Prisma 7 docs.

Line 27 links to the Prisma 6 upgrade guide. Since this guide is being updated for Prisma ORM 7, ensure the link correctly points to the Prisma 7 minimum Node.js requirements or an equivalent Prisma 7 reference.

---

39-48: Dependencies look correct for PostgreSQL adapter approach.

The setup properly installs @prisma/adapter-pg and pg for the PostgreSQL driver, plus tsx for the TypeScript seed script. Type dependencies (@types/pg) are also included.

---

54-68: Verify prisma/config API before publication.

The prisma.config.ts file uses defineConfig and env helpers from prisma/config. Please confirm these are valid and documented Prisma ORM APIs for your target version, as this pattern is not commonly referenced in standard Prisma documentation.

---

70-112: Schema and migration setup looks solid.

The schema correctly configures PostgreSQL as the provider with a custom generator output path (./generated). Since this guide uses direct Prisma ORM (not the @prisma/nuxt module), the custom output path is appropriate. The migration and dev server startup are properly sequenced.

---

173-257: Seeding implementation is well-structured.

The seed file properly instantiates the Prisma client with the PostgreSQL adapter, includes comprehensive sample data, and has proper error handling with disconnection. The npx prisma db seed command integration is correct.

---

259-346: Postgres setup and Vercel deployment sections are well-documented.

The instructions for creating a Prisma Postgres instance, configuring it in the app, and deploying to Vercel are clear and sequential. The .env example with the // edit-next-line comment properly indicates user action needed. Environment variable handling for deployment is appropriately emphasized.

---

349-351: Closing section is appropriate.

The "Considerations" section properly frames the guide as a starting point for Prisma Postgres integration with Nuxt.

---

119-143: Fix import/export mismatch in singleton pattern.

The lib/prisma.ts file exports prisma as a named export (line 134: export const prisma = ...), but the User.server.vue component imports it as a default export (line 142: import prisma from '~/lib/prisma'). This will cause a runtime error.

Update line 142 to use the correct named import syntax:

-      import prisma from '~/lib/prisma'
+      import { prisma } from '~/lib/prisma'

⛔ Skipped due to learnings

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.

---

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.}

[github-actions]

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

[github-actions]

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

• This PR does not change any pages in a way that would require a redirect.

[github-actions]

🍈 Lychee Link Check Report

Note: Links are cached for 5 minutes. Failed links (timeouts, rate limits) are retried in a second run with longer timeout.

📊 Results Overview

Status	Count
🔍 Total	2233
✅ Successful	2203
⏳ Timeouts	0
🔀 Redirected	6
👻 Excluded	22
❓ Unknown	0
🚫 Errors	1
⛔ Unsupported	1

Errors per input

Errors in 200-orm/800-more/300-upgrade-guides/200-upgrading-versions/400-upgrading-to-prisma-7.mdx

• [ERROR] file:///home/runner/work/docs/docs/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/orm/prisma-client/client-extensions | Cannot find file: File not found. Check if file exists and path is correct

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	e08a3f4
Status:	🚫  Build failed.

View logs

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

content/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdx (1)

14-16: Consider linking to the recommended alternative guide.

The warning helpfully directs users to "the general Nuxt guide" for Prisma 7 projects, but doesn't provide a direct link. Consider updating the warning to reference the updated Nuxt guide by name or link to ensure users can easily find the recommended approach.

content/800-guides/100-nuxt.mdx (1)

33-33: Update heading to use sentence case.

Per documentation guidelines, headings should use sentence case (only first word and proper nouns capitalized). Update line 33 from "1. Create a New Nuxt Project and install Prisma dependencies" to "1. Create a new Nuxt project and install Prisma dependencies".

Apply this diff:

-## 1. Create a New Nuxt Project and install Prisma dependencies
+## 1. Create a new Nuxt project and install Prisma dependencies

📜 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 a38e614 and 7413b69.

📒 Files selected for processing (2)

• content/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdx (1 hunks)
• content/800-guides/100-nuxt.mdx (9 hunks)

🧰 Additional context used

🧠 Learnings (5)

📓 Common learnings

Learnt from: ankur-arch
Repo: prisma/docs PR: 7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.

📚 Learning: 2025-10-08T16:22:57.129Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.

Applied to files:

• content/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdx

📚 Learning: 2025-10-08T16:23:00.388Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.

Applied to files:

• content/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdx

📚 Learning: 2025-10-09T21:32:50.340Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.

Applied to files:

• content/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdx
• content/800-guides/100-nuxt.mdx

📚 Learning: 2025-10-08T16:23:00.388Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".

Applied to files:

• content/800-guides/100-nuxt.mdx

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

• GitHub Check: Check internal links
• GitHub Check: Cloudflare Pages

🔇 Additional comments (8)

content/800-guides/100-nuxt.mdx (8)

1-22: Front matter and intro messaging are well-aligned with the guide's new direction.

The title, description, and learning objectives clearly signal the shift to direct Prisma ORM setup, which will help users understand the approach upfront.

---

44-46: Prisma initialization and schema configuration are well-structured.

The prisma init command and schema setup properly configure PostgreSQL as the datasource. The custom output path in the generator aligns with the intent to use direct Prisma ORM setup rather than the Nuxt module (which has limitations with custom output paths).

Also applies to: 74-102

---

117-136: Prisma Client singleton pattern with PostgreSQL adapter is correctly implemented.

The lib/prisma.ts file establishes the proper singleton pattern, prevents multiple client instances, and correctly integrates the PrismaPg adapter for PostgreSQL connections. The conditional preservation of the global instance is a solid practice for development environments.

---

138-148: Server component implementation is clean and handles the happy path and edge case well.

The User.server.vue component correctly queries the database and gracefully displays a fallback message when no user exists.

---

150-157: The app.vue update properly leverages Nuxt Islands for server-side rendering.

---

172-256: Seed script is well-structured with proper adapter usage and error handling.

The prisma/seed.ts file correctly sets up the PostgreSQL adapter, provides realistic sample data, and includes proper error handling with database disconnection. The structure aligns well with the singleton pattern established earlier in the guide.

---

258-346: Deployment guidance is comprehensive and includes critical safety checks.

The Prisma Postgres creation steps and Vercel deployment instructions are well-organized. The prominent warning about the DATABASE_URL environment variable being required will help prevent failed deployments. The verification steps give users confidence their setup is working.

---

49-67: Code is valid—prisma.config.ts with defineConfig and env is the standard approach in Prisma 7.

Prisma 7 supports a prisma.config.ts file and the defineConfig and env helpers from the prisma/config module. The configuration pattern shown in the guide is documented and correct.

[ankur-arch]

Suggested change

	## 1. Create a New Nuxt Project and install Prisma dependencies
	## 1. Create a New Nuxt Project and install Prisma ORM dependencies

[ankur-arch]

Why not use prisma init --db

[ankur-arch]

are the deps correct?

What about the type deps mentioned by Alberto?

[github-actions]

🍈 Lychee Link Check Report

Note: Links are cached for 5 minutes. Failed links (timeouts, rate limits) are retried in a second run with longer timeout.

📊 Results Overview

Status	Count
🔍 Total	2234
✅ Successful	2205
⏳ Timeouts	0
🔀 Redirected	3
👻 Excluded	23
❓ Unknown	0
🚫 Errors	2
⛔ Unsupported	1

Errors per input

Errors in 200-orm/100-prisma-schema/10-overview/03-generators.mdx

• [ERROR] https://nexusjs.org/docs/ | Error (cached)

Errors in 200-orm/800-more/300-upgrade-guides/200-upgrading-versions/400-upgrading-to-prisma-7.mdx

• [ERROR] file:///home/runner/work/docs/docs/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/orm/prisma-client/client-extensions | Cannot find file: File not found. Check if file exists and path is correct