feat(docs): add Next.js + Prisma Postgres on Vercel guide#7876
Closed
aidankmcalister wants to merge 1 commit into
Closed
feat(docs): add Next.js + Prisma Postgres on Vercel guide#7876aidankmcalister wants to merge 1 commit into
aidankmcalister wants to merge 1 commit into
Conversation
Adds /guides/postgres/nextjs-vercel — a zero-config focused quickstart explaining why Prisma Postgres works well with Vercel serverless functions: built-in pooling, single DATABASE_URL, no pgBouncer setup required. DR-8359 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
🍈 Lychee Link Check Report8 links: ✅ All links are working!Full Statistics Table
|
Contributor
WalkthroughThis PR adds a new documentation guide for integrating Prisma Postgres with Next.js applications deployed on Vercel. The guide provides end-to-end instructions covering project scaffolding, Prisma setup, schema definition, database configuration, runtime client implementation, and deployment steps, with an entry added to the Postgres guides metadata index. ChangesNext.js on Vercel Integration Guide
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/docs/content/docs/guides/postgres/nextjs-vercel.mdx`:
- Around line 54-56: Update the dev dependency installation step by removing the
unused "tsx" package from the command that currently reads "npm install prisma
tsx --save-dev"; change it to only install the required dev dependency (prisma)
and ensure any later references to ".tsx" remain as file extensions only, not as
a package requirement in the guide.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 906ee01b-8f64-4210-80d4-8af403f9bf55
📒 Files selected for processing (2)
apps/docs/content/docs/guides/postgres/meta.jsonapps/docs/content/docs/guides/postgres/nextjs-vercel.mdx
Comment on lines
+54
to
+56
| ```npm | ||
| npm install prisma tsx --save-dev | ||
| ``` |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check if tsx is used in package.json scripts or referenced in the guide
rg -n 'tsx' apps/docs/content/docs/guides/postgres/nextjs-vercel.mdxRepository: prisma/web
Length of output: 169
Remove unnecessary tsx dependency.
The tsx package is installed on line 55 but never used in any subsequent steps. The guide runs Prisma CLI commands (npx prisma init, npx create-db) and Next.js framework code, neither of which requires tsx. The references to "tsx" elsewhere in the guide are only file extensions (.tsx), not invocations of the package. Removing it simplifies the installation command:
-npm install prisma tsx --save-dev
+npm install prisma --save-dev🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/docs/content/docs/guides/postgres/nextjs-vercel.mdx` around lines 54 -
56, Update the dev dependency installation step by removing the unused "tsx"
package from the command that currently reads "npm install prisma tsx
--save-dev"; change it to only install the required dev dependency (prisma) and
ensure any later references to ".tsx" remain as file extensions only, not as a
package requirement in the guide.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/guides/postgres/nextjs-vercelcovering the full path fromcreate-next-appto a deployed Vercel app backed by Prisma Postgresprisma init, Prisma schema, migrations, andpostinstallhook for Vercel buildsapps/docs/content/docs/guides/postgres/meta.jsonto surface the guide in sidebar navigationTest plan
/docs/v7/guides/postgres/nextjs-vercelnextjs-vercelappears in the Postgres guides sidebar🤖 Generated with Claude Code
Summary by CodeRabbit