fix(docs): updated many bash codeblocks to npm to make use of the package manager selectors#7528
Merged
aidankmcalister merged 7 commits intomainfrom Feb 23, 2026
Merged
Conversation
… package manager selector
Contributor
🍈 Lychee Link Check Report3664 links: ✅ All links are working!Full Statistics Table
|
aidankmcalister
requested review from
AmanVarshney01,
ArthurGamby,
ankur-arch and
mhartington
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (11)
💤 Files with no reviewable changes (1)
✅ Files skipped from review due to trivial changes (3)
WalkthroughThis PR standardizes fenced-code language specifiers (mostly Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (4)
apps/docs/content/docs.v6/orm/reference/prisma-config-reference.mdx (1)
760-764:⚠️ Potential issue | 🔴 CriticalShell commands cannot use the npm identifier.
This code block contains
cd src(line 761), which is a shell navigation command, not an npm/package manager command. Package manager selectors are designed to toggle between npm/yarn/pnpm/bun equivalents and cannot handle shell-specific commands likecd.🔧 Proposed fix: Keep this block as bash
-```npm +```bash cd src npx prisma validate # → Error: Could not find Prisma Schema...Alternatively, if package manager selectors are needed, consider splitting into separate blocks or removing the `cd` command entirely since the text already explains "Run from a subdirectory (fails):". </details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@apps/docs/content/docs.v6/orm/reference/prisma-config-reference.mdxaround
lines 760 - 764, The fenced code block is labeled as npm but contains a shell
navigation command ("cd src") which breaks package-manager selectors; change the
block's language fromnpm tobash (or split into two blocks) so the "cd
src" and "npx prisma validate" lines are treated as shell commands, or
alternatively remove the "cd src" line if you must keep an npm selector; update
the block that currently starts with ```npm and includes "cd src" and "npx
prisma validate" accordingly.</details> </blockquote></details> <details> <summary>apps/docs/content/docs/orm/reference/prisma-config-reference.mdx (1)</summary><blockquote> `704-708`: _⚠️ Potential issue_ | _🟡 Minor_ **Revert to `bash` — this block contains shell commands.** The code block includes `cd src`, which is a shell command demonstrating directory navigation. Package manager selectors don't apply here since the block's purpose is to show what happens when running Prisma CLI from a subdirectory. <details> <summary>Suggested fix</summary> ```diff -```npm +```bash cd src npx prisma validate # → Error: Could not find Prisma Schema... ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs/orm/reference/prisma-config-reference.mdx` around lines 704 - 708, The fenced code block that shows running Prisma from a subdirectory is incorrectly labeled with the npm language tag; change the code fence language from "npm" to "bash" for the block containing the commands "cd src" and "npx prisma validate" so the shell commands (and their output comment "# → Error: Could not find Prisma Schema...") are rendered and highlighted as shell/bash rather than as a package-manager snippet. ``` </details> </blockquote></details> <details> <summary>apps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx (1)</summary><blockquote> `54-58`: _⚠️ Potential issue_ | _🟡 Minor_ **Revert to `bash` — this block contains shell commands.** The code block includes `mkdir` and `cd`, which are shell commands for creating and navigating directories. These aren't package manager commands, so the selector doesn't apply here. <details> <summary>Suggested fix</summary> ```diff -```npm +```bash mkdir prisma-deno-deploy cd prisma-deno-deploy npx prisma@latest init --db ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@apps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx
around lines 54 - 58, Change the fenced code block language tag from "npm" to
"bash" so the shell commands (mkdir, cd, npx prisma@latest init --db) are
correctly highlighted and treated as shell commands; locate the fenced block
that currently begins withnpm and replace that tag withbash.</details> </blockquote></details> <details> <summary>apps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-cloudflare.mdx (1)</summary><blockquote> `236-241`: _⚠️ Potential issue_ | _🟡 Minor_ **Mixed shell and npm commands may not work well with package manager selectors.** This code block contains the shell command `cd prisma-cloudflare-worker-example` alongside npm commands. Package manager selectors typically convert npm commands to yarn/pnpm equivalents, but `cd` is a shell command with no package manager equivalent. Consider splitting this into separate blocks — one `bash` block for the shell navigation and separate `npm` blocks for the package manager commands: <details> <summary>📝 Suggested restructuring</summary> ```diff -```npm -npm create cloudflare@latest prisma-cloudflare-worker-example -- --type hello-world -cd prisma-cloudflare-worker-example -npm install prisma --save-dev && npm install `@prisma/client` -npx prisma init --output ../generated/prisma -``` +```npm +npm create cloudflare@latest prisma-cloudflare-worker-example -- --type hello-world +``` + +```bash +cd prisma-cloudflare-worker-example +``` + +```npm +npm install prisma --save-dev && npm install `@prisma/client` +npx prisma init --output ../generated/prisma +``` ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-cloudflare.mdx` around lines 236 - 241, The code block that begins with "npm create cloudflare@latest prisma-cloudflare-worker-example -- --type hello-world" mixes shell navigation (cd prisma-cloudflare-worker-example) with npm commands which breaks package-manager selectors; split it into three blocks: an npm block containing the create command, a bash block containing the cd command, and a second npm block containing the install and npx prisma init lines so package manager selectors only convert package manager commands. ``` </details> </blockquote></details> </blockquote></details>🧹 Nitpick comments (8)
apps/docs/content/docs.v6/guides/clerk-nextjs.mdx (1)
477-480: Non-npm command included in npm-tagged block.The
ngrok http 3000line is a CLI tool invocation, not an npm command. If your package manager selector feature attempts to transform all lines innpm-tagged blocks, this could produce incorrect output (e.g.,yarn ngrok http 3000).Consider splitting into two separate blocks—one
npmblock for the install command and onebashblock for the ngrok invocation:💡 Suggested refactor
-```npm -npm install --global ngrok -ngrok http 3000 -``` +```npm +npm install --global ngrok +``` + +```bash +ngrok http 3000 +```🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs.v6/guides/clerk-nextjs.mdx` around lines 477 - 480, The npm-marked code block contains a non-npm CLI invocation ("ngrok http 3000"); split the single block into two blocks so package-manager transforms won't alter the ngrok command: keep the "npm install --global ngrok" line in an npm-marked block and move the "ngrok http 3000" line into a separate bash (or shell) block, updating the surrounding fenced code markers accordingly so the install and runtime commands are correctly typed.apps/docs/content/docs.v6/guides/sveltekit.mdx (1)
46-49: Mixed shell and npm commands in one block.This block contains
cd sveltekit-prisma(a shell command) alongsidenpm run dev. Thenpmtag is primarily appropriate for the second line. If your package manager selectors don't transform shell commands likecd, this should work fine. Just wanted to flag the mixed content for awareness.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs.v6/guides/sveltekit.mdx` around lines 46 - 49, The fenced code block currently labeled ```npm contains a shell command `cd sveltekit-prisma` and `npm run dev`; update it so shell and package-manager commands are correctly tagged—either split into two blocks (one ```bash with `cd sveltekit-prisma` and one ```npm with `npm run dev`) or change the single fence to a shell tag like ```bash so both commands use the appropriate shell highlighting; locate the block that begins with ```npm and adjust accordingly.apps/docs/content/docs/guides/switch-to-prisma-orm/from-sql-orms.mdx (1)
66-70: Shell commandmkdirincluded in npm-tagged block.This block starts with
mkdir -p prisma/migrations/0_init, which is a shell command unrelated to npm. If your package manager selector transforms this, it could produce nonsensical output.Consider keeping the
mkdirin a separatebashblock or combining all commands with proper context:💡 Suggested refactor
-```npm -mkdir -p prisma/migrations/0_init -npx prisma migrate diff --from-empty --to-schema prisma/schema.prisma --script > prisma/migrations/0_init/migration.sql -npx prisma migrate resolve --applied 0_init -``` +```bash +mkdir -p prisma/migrations/0_init +``` + +```npm +npx prisma migrate diff --from-empty --to-schema prisma/schema.prisma --script > prisma/migrations/0_init/migration.sql +npx prisma migrate resolve --applied 0_init +```🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs/guides/switch-to-prisma-orm/from-sql-orms.mdx` around lines 66 - 70, Separate the shell-only mkdir command from the npm-labeled code block: move the line "mkdir -p prisma/migrations/0_init" into its own fencing using ```bash and leave the two npx commands ("npx prisma migrate diff --from-empty --to-schema prisma/schema.prisma --script > prisma/migrations/0_init/migration.sql" and "npx prisma migrate resolve --applied 0_init") inside the existing ```npm fenced block so the package-manager selector won't mislabel a shell command.apps/docs/content/docs.v6/guides/data-dog.mdx (1)
49-53: Shell commands mixed with npm in tagged block.This block contains
mkdirandcd(shell commands) alongsidenpm init -y. If your package manager selectors operate on this block, the shell commands could be incorrectly transformed.Consider splitting:
💡 Suggested refactor
-```npm -mkdir prisma-datadog-tracing -cd prisma-datadog-tracing -npm init -y -``` +```bash +mkdir prisma-datadog-tracing +cd prisma-datadog-tracing +``` + +```npm +npm init -y +```🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs.v6/guides/data-dog.mdx` around lines 49 - 53, The fenced code block that currently mixes shell commands ("mkdir prisma-datadog-tracing" and "cd prisma-datadog-tracing") with an npm command ("npm init -y") should be split into two separate fenced blocks: one with a bash shell fence for the mkdir and cd commands, and a separate npm fence for the npm init -y command; update the existing block that contains "mkdir prisma-datadog-tracing", "cd prisma-datadog-tracing", and "npm init -y" to instead use a ```bash fence for the two shell lines and a ```npm fence for the npm init line so package-manager selectors won't transform the shell commands.apps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/kysely.mdx (1)
21-25: Mixed shell and npm commands in annpmcode block.This block contains
mkdirandcdwhich are pure shell commands, alongsidenpm init. The package manager selector would only be meaningful fornpm init -y, butmkdirandcddon't have npm/yarn/pnpm equivalents.Consider splitting this into a
bashblock for the shell commands and annpmblock fornpm init -y, or keeping it asbashsince the block is primarily about directory setup.✏️ Option: Split into separate blocks
-```npm +```bash mkdir kysely-quickstart cd kysely-quickstart +``` + +```npm npm init -y</details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@apps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/kysely.mdx
around lines 21 - 25, The code block mixes shell commands ("mkdir
kysely-quickstart" and "cd kysely-quickstart") with an npm command ("npm init
-y"); split them so shell commands are in a bash block and the package manager
command is in an npm block (or make the entire snippet bash). Update the
existing block that contains "mkdir kysely-quickstart", "cd kysely-quickstart",
and "npm init -y" by extracting the first two into abashblock and
leaving "npm init -y" in a separatenpmblock, or convert the whole block
tobashif you prefer a single block.</details> </blockquote></details> <details> <summary>apps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/typeorm.mdx (1)</summary><blockquote> `44-47`: **Mixed shell and npm commands in an `npm` code block.** This block contains `cd typeorm-quickstart` (a shell command) alongside `npm install`. The `cd` command won't have an equivalent when the package manager selector converts to yarn/pnpm. Consider either keeping this as `bash` or splitting the commands. <details> <summary>✏️ Option: Split into separate blocks</summary> ```diff -```npm +```bash cd typeorm-quickstart +``` + +```npm npm install ``` ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs.v6/`(index)/prisma-postgres/quickstart/typeorm.mdx around lines 44 - 47, The code block mixes a shell command ("cd typeorm-quickstart") with an npm command, which breaks package-manager selectors; either change the block language to bash (e.g., replace the fenced block language from npm to bash) so both commands remain together, or split into two blocks—one fenced as bash containing "cd typeorm-quickstart" and a second fenced as npm containing "npm install"—so the package-manager selector can convert the npm block correctly. ``` </details> </blockquote></details> <details> <summary>apps/docs/content/docs/guides/making-guides.mdx (1)</summary><blockquote> `275-279`: **Mixed shell and npm commands in an `npm` code block.** This template example includes `cd my-app` (a shell command) alongside `npx create-next-app`. Since this is a guide template that other documentation authors will follow, consider being explicit about the correct pattern. The guide itself at lines 83-84 correctly states: - Use ` ```npm ` for package manager commands - Use ` ```bash ` for shell commands The template should model this distinction. <details> <summary>✏️ Suggested fix for template consistency</summary> ```diff -```npm -# Example command -npx create-next-app@latest my-app +```npm +npx create-next-app@latest my-app +``` + +```bash cd my-app ``` ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@apps/docs/content/docs/guides/making-guides.mdxaround lines 275 - 279,
Split the mixed commands into two fenced blocks as the guide prescribes: wrap
the package manager commandnpx create-next-app@latest my-appin anpm block and then put the shell command `cd my-app` in a separatebash block;
update the existing triple-backtick fences around the example so thenpxline
is inside anpm fence and the `cd my-app` line is inside abash fence to
model the correct pattern used elsewhere in the guide.</details> </blockquote></details> <details> <summary>apps/docs/content/docs.v6/guides/github-actions.mdx (1)</summary><blockquote> `30-33`: **Mixed shell and npm commands in an `npm` code block.** This block combines `mkdir ... && cd ...` (shell commands) with `npm init -y`. The shell commands won't translate when users select a different package manager. Consider keeping this as `bash` or splitting the initialization steps. <details> <summary>✏️ Option: Split into separate blocks</summary> ```diff -```npm +```bash mkdir prisma-gha-demo && cd prisma-gha-demo +``` + +```npm npm init -y ``` ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against the current code and only fix it if needed. In `@apps/docs/content/docs.v6/guides/github-actions.mdx` around lines 30 - 33, The current npm code block mixes shell commands ("mkdir prisma-gha-demo && cd prisma-gha-demo") with an npm command ("npm init -y"), which confuses package manager-specific selections; fix by splitting or retagging: either change the entire block to a bash code block for both lines, or split into two blocks—one bash block containing "mkdir prisma-gha-demo && cd prisma-gha-demo" and a separate npm block with "npm init -y"—by editing the code block in the docs.v6/guides/github-actions.mdx that currently contains those two commands. ``` </details> </blockquote></details> </blockquote></details> <details> <summary>🤖 Prompt for all review comments with AI agents</summary>Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In
@apps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-cloudflare.mdx:
- Around line 236-241: The code block that begins with "npm create
cloudflare@latest prisma-cloudflare-worker-example -- --type hello-world" mixes
shell navigation (cd prisma-cloudflare-worker-example) with npm commands which
breaks package-manager selectors; split it into three blocks: an npm block
containing the create command, a bash block containing the cd command, and a
second npm block containing the install and npx prisma init lines so package
manager selectors only convert package manager commands.In
@apps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx:
- Around line 54-58: Change the fenced code block language tag from "npm" to
"bash" so the shell commands (mkdir, cd, npx prisma@latest init --db) are
correctly highlighted and treated as shell commands; locate the fenced block
that currently begins withnpm and replace that tag withbash.In
@apps/docs/content/docs.v6/orm/reference/prisma-config-reference.mdx:
- Around line 760-764: The fenced code block is labeled as npm but contains a
shell navigation command ("cd src") which breaks package-manager selectors;
change the block's language fromnpm tobash (or split into two blocks) so
the "cd src" and "npx prisma validate" lines are treated as shell commands, or
alternatively remove the "cd src" line if you must keep an npm selector; update
the block that currently starts with ```npm and includes "cd src" and "npx
prisma validate" accordingly.In
@apps/docs/content/docs/orm/reference/prisma-config-reference.mdx:
- Around line 704-708: The fenced code block that shows running Prisma from a
subdirectory is incorrectly labeled with the npm language tag; change the code
fence language from "npm" to "bash" for the block containing the commands "cd
src" and "npx prisma validate" so the shell commands (and their output comment
"# → Error: Could not find Prisma Schema...") are rendered and highlighted as
shell/bash rather than as a package-manager snippet.
Nitpick comments:
In@apps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/kysely.mdx:
- Around line 21-25: The code block mixes shell commands ("mkdir
kysely-quickstart" and "cd kysely-quickstart") with an npm command ("npm init
-y"); split them so shell commands are in a bash block and the package manager
command is in an npm block (or make the entire snippet bash). Update the
existing block that contains "mkdir kysely-quickstart", "cd kysely-quickstart",
and "npm init -y" by extracting the first two into abashblock and
leaving "npm init -y" in a separatenpmblock, or convert the whole block
tobashif you prefer a single block.In
@apps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/typeorm.mdx:
- Around line 44-47: The code block mixes a shell command ("cd
typeorm-quickstart") with an npm command, which breaks package-manager
selectors; either change the block language to bash (e.g., replace the fenced
block language from npm to bash) so both commands remain together, or split into
two blocks—one fenced as bash containing "cd typeorm-quickstart" and a second
fenced as npm containing "npm install"—so the package-manager selector can
convert the npm block correctly.In
@apps/docs/content/docs.v6/guides/clerk-nextjs.mdx:
- Around line 477-480: The npm-marked code block contains a non-npm CLI
invocation ("ngrok http 3000"); split the single block into two blocks so
package-manager transforms won't alter the ngrok command: keep the "npm install
--global ngrok" line in an npm-marked block and move the "ngrok http 3000" line
into a separate bash (or shell) block, updating the surrounding fenced code
markers accordingly so the install and runtime commands are correctly typed.In
@apps/docs/content/docs.v6/guides/data-dog.mdx:
- Around line 49-53: The fenced code block that currently mixes shell commands
("mkdir prisma-datadog-tracing" and "cd prisma-datadog-tracing") with an npm
command ("npm init -y") should be split into two separate fenced blocks: one
with a bash shell fence for the mkdir and cd commands, and a separate npm fence
for the npm init -y command; update the existing block that contains "mkdir
prisma-datadog-tracing", "cd prisma-datadog-tracing", and "npm init -y" to
instead use abash fence for the two shell lines and anpm fence for the
npm init line so package-manager selectors won't transform the shell commands.In
@apps/docs/content/docs.v6/guides/github-actions.mdx:
- Around line 30-33: The current npm code block mixes shell commands ("mkdir
prisma-gha-demo && cd prisma-gha-demo") with an npm command ("npm init -y"),
which confuses package manager-specific selections; fix by splitting or
retagging: either change the entire block to a bash code block for both lines,
or split into two blocks—one bash block containing "mkdir prisma-gha-demo && cd
prisma-gha-demo" and a separate npm block with "npm init -y"—by editing the code
block in the docs.v6/guides/github-actions.mdx that currently contains those two
commands.In
@apps/docs/content/docs.v6/guides/sveltekit.mdx:
- Around line 46-49: The fenced code block currently labeled
npm contains a shell command `cd sveltekit-prisma` and `npm run dev`; update it so shell and package-manager commands are correctly tagged—either split into two blocks (onebash withcd sveltekit-prismaand onenpm with `npm run dev`) or change the single fence to a shell tag likebash so both commands use the
appropriate shell highlighting; locate the block that begins with ```npm and
adjust accordingly.In
@apps/docs/content/docs/guides/making-guides.mdx:
- Around line 275-279: Split the mixed commands into two fenced blocks as the
guide prescribes: wrap the package manager commandnpx create-next-app@latest my-appin anpm block and then put the shell command `cd my-app` in a separatebash block; update the existing triple-backtick fences around the
example so thenpxline is inside anpm fence and the `cd my-app` line is inside abash fence to model the correct pattern used elsewhere in the guide.In
@apps/docs/content/docs/guides/switch-to-prisma-orm/from-sql-orms.mdx:
- Around line 66-70: Separate the shell-only mkdir command from the npm-labeled
code block: move the line "mkdir -p prisma/migrations/0_init" into its own
fencing usingbash and leave the two npx commands ("npx prisma migrate diff --from-empty --to-schema prisma/schema.prisma --script > prisma/migrations/0_init/migration.sql" and "npx prisma migrate resolve --applied 0_init") inside the existingnpm fenced block so the
package-manager selector won't mislabel a shell command.</details> --- <details> <summary>ℹ️ Review info</summary> **Configuration used**: Path: .coderabbit.yaml **Review profile**: CHILL **Plan**: Pro <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between 8d2b4405a51cbe473c840b2ec490f2665dbbbff1 and 0bd2111df23f24b293d72de38f49175b9c64412d. </details> <details> <summary>📒 Files selected for processing (44)</summary> * `apps/docs/content/docs.v6/(index)/prisma-postgres/from-the-cli.mdx` * `apps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/drizzle-orm.mdx` * `apps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/kysely.mdx` * `apps/docs/content/docs.v6/(index)/prisma-postgres/quickstart/typeorm.mdx` * `apps/docs/content/docs.v6/ai/tutorials/linktree-clone.mdx` * `apps/docs/content/docs.v6/guides/betterauth-astro.mdx` * `apps/docs/content/docs.v6/guides/clerk-astro.mdx` * `apps/docs/content/docs.v6/guides/clerk-nextjs.mdx` * `apps/docs/content/docs.v6/guides/cloudflare-d1.mdx` * `apps/docs/content/docs.v6/guides/cloudflare-workers.mdx` * `apps/docs/content/docs.v6/guides/data-dog.mdx` * `apps/docs/content/docs.v6/guides/docker.mdx` * `apps/docs/content/docs.v6/guides/github-actions.mdx` * `apps/docs/content/docs.v6/guides/hono.mdx` * `apps/docs/content/docs.v6/guides/management-api-basic.mdx` * `apps/docs/content/docs.v6/guides/migrate-from-typeorm.mdx` * `apps/docs/content/docs.v6/guides/nuxt.mdx` * `apps/docs/content/docs.v6/guides/permit-io-access-control.mdx` * `apps/docs/content/docs.v6/guides/solid-start.mdx` * `apps/docs/content/docs.v6/guides/sveltekit.mdx` * `apps/docs/content/docs.v6/guides/tanstack-start.mdx` * `apps/docs/content/docs.v6/guides/turborepo.mdx` * `apps/docs/content/docs.v6/orm/more/upgrades/older-versions.mdx` * `apps/docs/content/docs.v6/orm/more/upgrades/to-v7.mdx` * `apps/docs/content/docs.v6/orm/overview/databases/cloudflare-d1.mdx` * `apps/docs/content/docs.v6/orm/overview/databases/database-drivers.mdx` * `apps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-cloudflare.mdx` * `apps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-deno-deploy.mdx` * `apps/docs/content/docs.v6/orm/prisma-client/deployment/edge/deploy-to-vercel.mdx` * `apps/docs/content/docs.v6/orm/prisma-client/deployment/serverless/deploy-to-vercel.mdx` * `apps/docs/content/docs.v6/orm/reference/prisma-config-reference.mdx` * `apps/docs/content/docs.v6/platform/platform-cli/commands.mdx` * `apps/docs/content/docs.v6/postgres/integrations/netlify.mdx` * `apps/docs/content/docs/ai/tutorials/typefully-clone.mdx` * `apps/docs/content/docs/guides/deployment/cloudflare-d1.mdx` * `apps/docs/content/docs/guides/making-guides.mdx` * `apps/docs/content/docs/guides/switch-to-prisma-orm/from-sql-orms.mdx` * `apps/docs/content/docs/orm/core-concepts/supported-databases/mysql.mdx` * `apps/docs/content/docs/orm/index.mdx` * `apps/docs/content/docs/orm/reference/prisma-cli-reference.mdx` * `apps/docs/content/docs/orm/reference/prisma-config-reference.mdx` * `apps/docs/content/docs/postgres/database/local-development.mdx` * `apps/docs/content/docs/studio/getting-started.mdx` * `apps/docs/content/docs/studio/index.mdx` </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
ArthurGamby
approved these changes
Feb 23, 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.
Linear: DR-7389
Summary by CodeRabbit