docs(compute): prisma.compute.ts configuration reference + Nuxt/Astro framework lists#7950
Merged
Conversation
New Reference page documenting the typed config file: the single-app and monorepo (apps) shapes, every app field (name/root/framework/entry/httpPort/ env/build), env shapes, build settings (incl. the nuxt/astro caveat), file discovery, monorepo deploy-all/target selection, and how config defaults interact with flags. Linked into the compute section nav before cli-reference.
|
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 (2)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughAdds a new ChangesPrisma Compute Documentation Updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Contributor
🍈 Lychee Link Check Report52 links: ✅ All links are working!Full Statistics Table
|
Nuxt and Astro deploy support is live, but several pages still enumerated only nextjs/hono/tanstack-start/bun for --framework and in prose (while --build-type already listed nuxt/astro). Bring the deploy quickstart, getting-started, cli-reference --framework, and limitations in line so the full set is consistent: nextjs, nuxt, astro, hono, tanstack-start, bun.
AmanVarshney01
changed the title
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
app build is not a dev server, so 'a dev server can only run one app' mis-justified the build case. State the real reason: build and run have no all-apps form, unlike deploy.
Skills moved to the prisma/skills repo (skills at the root). Update the install commands to npx skills add prisma/skills --skill prisma-compute, which is the Compute deploy skill (the prisma-cli skill is now the ORM CLI reference). Drop the obsolete #cli-v<version> pin — prisma/skills is not versioned by CLI tag.
Restructure with commas, colons, parentheses, and separate sentences instead.
Audited every documented CLI invocation against prisma-cli: - Remove branch show and branch use; the CLI only has branch list. - Stop claiming there is no database command. It exists (database list/show/create/connection), so add it to the command groups and drop it from the 'no X command' list. (No full reference section yet.) All other commands, flags, build types, error codes, and env vars already matched.
![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/compute/getting-started.mdx`:
- Around line 176-178: Change the code fence delimiters from bash to npm for
package manager install commands to enable auto-tabbed rendering across
different package managers. In
apps/docs/content/docs/compute/getting-started.mdx at lines 176-178, change the
fence from `bash` to `npm` for the `npx skills add prisma/skills --skill
prisma-compute` command. In apps/docs/content/docs/compute/cli-reference.mdx at
lines 174-176, apply the same change from `bash` to `npm` fence for the
identical install command. This allows the documentation tooling to
automatically generate tabs for alternative package managers (bun, yarn, pnpm)
alongside the default npm rendering.
🪄 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: 9d364926-bf41-46cb-8565-e10dca9bca24
📒 Files selected for processing (7)
apps/docs/content/docs/(index)/prisma-compute/deploy.mdxapps/docs/content/docs/compute/branching.mdxapps/docs/content/docs/compute/cli-reference.mdxapps/docs/content/docs/compute/configuration.mdxapps/docs/content/docs/compute/getting-started.mdxapps/docs/content/docs/compute/limitations.mdxapps/docs/content/docs/compute/meta.json
So the docs tooling auto-generates the package-manager tabs (bun/yarn/pnpm) for the skills install command, per the apps/docs convention.
ankur-arch
reviewed
Jun 16, 2026
ankur-arch
approved these changes
Jun 16, 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.
What
New Configuration reference page for the
prisma.compute.tsfile (shipped in feat: typed prisma.compute.ts compute config prisma-cli#84), slotted into the Compute section nav under Reference, beforecli-reference. Covers:appshape anddefineComputeConfigname,root,framework,entry,httpPort,env,build) as a tableenvshapes and the committed-file secrets caveatbuildsettings incl. the nuxt/astro "no build block" ruleappsmap, deploy-all vs. targeting one app, build/run needing a targetFramework-list consistency. Nuxt and Astro deploy support is live, but the quickstart, getting-started,
cli-reference--framework, and limitations still listed only nextjs/hono/tanstack-start/bun (while--build-typealready listed nuxt/astro). Updated all of them to the full set:nextjs,nuxt,astro,hono,tanstack-start,bun.Verification
lint:linksandlint:codepass; cross-link anchors resolve; formatted with oxfmt.Summary by CodeRabbit
prisma.compute.ts(and JS/MTS variants), covering supported fields, env handling, build behavior, and monorepo discovery rules.npx, and refreshed branch-related commands.