feat(docs): add Netlify and Vercel Compute migration guides#7868
Closed
aidankmcalister wants to merge 2 commits intodocs/prisma-compute-quickstartfrom
Closed
feat(docs): add Netlify and Vercel Compute migration guides#7868aidankmcalister wants to merge 2 commits intodocs/prisma-compute-quickstartfrom
aidankmcalister wants to merge 2 commits intodocs/prisma-compute-quickstartfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✅ Files skipped from review due to trivial changes (3)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughAdds public and internal "Migration guides" (Vercel, Netlify) and metadata, plus related Compute docs updates (TanStack Start quickstart and Next.js pnpm troubleshooting) to support migrating Vercel/Netlify deployments to Prisma Compute. ChangesMigration guides + navigation and supporting docs
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Comment |
Contributor
🍈 Lychee Link Check Report26 links: ✅ All links are working!Full Statistics Table
|
|
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: 6
🤖 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/compute-internal/guides/netlify.mdx`:
- Around line 130-142: Add a clear, explicit warning inside the "Export Netlify
environment variables with the CLI" Accordion telling readers that the generated
.env.netlify file contains sensitive production secrets and must be kept local
only (do not commit), and instruct them to add .env.netlify to .gitignore; refer
to the Accordion title "Export Netlify environment variables with the CLI" and
mention the filename `.env.netlify` and `.gitignore` so maintainers can place
the note immediately after the netlify CLI example.
In `@apps/docs/content/docs/compute-internal/guides/vercel.mdx`:
- Around line 129-134: After the `vercel env pull .env.vercel
--environment=production` example in the Vercel guide, add a concise
secret-handling warning instructing readers that `.env.vercel` contains
production secrets, must not be committed to version control, and should be
securely deleted after migrating required values; update the paragraph near the
existing code block and reference `.env.vercel` and the surrounding Vercel env
pull example so the warning appears immediately after the shown command.
- Around line 87-90: Replace the unsafe deletion command "rm -rf .next
node_modules ~/package-lock.json" with a repo-local cleanup (e.g., remove "~/"
so it targets "./package-lock.json" or just ".next" and "node_modules") and add
a short note telling users to manually check and remove ~/package-lock.json only
if they confirm it is an accidental home-directory file; update the code block
that currently contains that command accordingly.
In `@apps/docs/content/docs/compute/guides/netlify.mdx`:
- Around line 130-135: Add an explicit secret-hygiene warning in the Netlify env
export example in apps/docs/content/docs/compute/guides/netlify.mdx: after the
bash block that shows `netlify env:list --context production --plain >
.env.netlify` insert a single-sentence caution that `.env.netlify` is sensitive,
must not be committed to version control, and should be deleted after copying
needed values (so readers know to treat the exported file as secrets and remove
it after migration).
In `@apps/docs/content/docs/compute/guides/vercel.mdx`:
- Around line 121-129: Add an explicit warning under the "Pull Vercel
environment variables with the CLI" Accordion that pulled files like
`.env.vercel` contain production secrets and must not be committed; instruct
readers to add `.env.vercel` to `.gitignore` and treat it as sensitive
local-only data, placed immediately after the `vercel env pull .env.vercel
--environment=production` example and before the paragraph that lists runtime
values like `DATABASE_URL`.
- Around line 67-72: Update the install/build instructions so they aren't
npm-specific: replace or augment the lines containing "npm install" and "npm run
build" with a generalized wording and add a brief note that projects using pnpm
or yarn should run the equivalent commands (e.g., pnpm install / pnpm build or
yarn install / yarn build) so the doc supports different package managers.
🪄 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: f55b68d0-4fdd-4b37-8bad-fc893ac058ed
📒 Files selected for processing (10)
apps/docs/content/docs/compute-internal/guides/meta.jsonapps/docs/content/docs/compute-internal/guides/netlify.mdxapps/docs/content/docs/compute-internal/guides/vercel.mdxapps/docs/content/docs/compute-internal/limitations.mdxapps/docs/content/docs/compute-internal/meta.jsonapps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdxapps/docs/content/docs/compute/guides/meta.jsonapps/docs/content/docs/compute/guides/netlify.mdxapps/docs/content/docs/compute/guides/vercel.mdxapps/docs/content/docs/compute/meta.json
mhartington
pushed a commit
that referenced
this pull request
May 5, 2026
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
2 participants
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
Adds migration guides for moving existing Netlify and Vercel deployments to Prisma Compute, in both the public and internal docs.
compute/guides/netlify.mdx,compute/guides/vercel.mdx— public migration guidescompute-internal/guides/netlify.mdx,compute-internal/guides/vercel.mdx— internal versions using@prisma/cli@previewEach guide covers prerequisites, framework prep (Next.js, TanStack Start, Astro, Nuxt, Bun), local build, deploy, and traffic cutover. Framework prep is in expand-by-default accordions so users can jump straight to their stack.
TanStack Start specifics:
vite.config.tsswap from@netlify/vite-plugin-tanstack-start→nitro/vite(diff-highlighted)vite.config.tschange is needed since Vercel already uses Nitro--entry .output/server/index.mjsflag in the deploy stepSummary by CodeRabbit