Fix default --output value for prisma init

[MansurAliKoroglu]

With 6.15.0 cli when I run npx prisma init it generates output with different default than documented.

generator client {
  provider = "prisma-client-js"
  output   = "../generated/prisma"
}

Summary by CodeRabbit

• Documentation
  • Updated CLI reference for the init command to reflect the new default Prisma Client output path (--output) now set to ../generated/prisma (previously node_modules/.prisma/client).
  • Improves accuracy and clarity of setup instructions; no functional changes to the CLI or behavior.

[coderabbitai]

Walkthrough

Documentation update: in the Prisma CLI reference, the init command’s Options table changes the default Prisma Client --output path from node_modules/.prisma/client to ../generated/prisma. No code or control-flow changes.

Changes

Cohort / File(s)	Summary of Changes
Docs: Prisma CLI reference content/200-orm/500-reference/200-prisma-cli-reference.mdx	Updated the documented default value for the Prisma Client --output option from node_modules/.prisma/client to ../generated/prisma. No other edits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix import paths in getting started tutorials #7100 — Also updates docs regarding the generated Prisma client path; aligns default to ../generated/prisma.
• clerk updates #7073 — Adjusts Prisma client documentation for output/import paths related to generated client.

Suggested reviewers

• mhessdev
• nikolasburk
• nurul3101

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly and accurately describes the primary change introduced in the pull request, namely adjusting the default output value for the prisma init command. It is concise and focuses on the main update without extraneous details, making it easy for reviewers to understand the purpose of the changeset.
Description Check	✅ Passed	The description explains the discrepancy between the documented default output path and the actual behavior of the CLI, directly relating to the change made in the pull request. It describes the context of the issue and the specific CLI version affected, providing relevant information for reviewers.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

content/200-orm/500-reference/200-prisma-cli-reference.mdx (2)

138-138: Default path update looks correct; consider a short clarifier.

Changing the init default for --output to ../generated/prisma aligns with current guidance to use a custom output and the ongoing shift away from generating into node_modules by default. A brief note that this default applies to the schema created by prisma init (while prisma generate still defaults to node_modules/.prisma/client unless an output is set) would prevent confusion. (prisma.io, prismagraphql.com)

If possible, please confirm with a quick local check on Prisma CLI 6.15.0: run npx prisma@6.15.0 init in a temp folder and verify the generated schema.prisma includes output = "../generated/prisma". The 6.15.0 release comms also reinforce the “custom output” direction. (prisma.io, github.com)

---

329-332: Keep init examples consistent: add output here too.

The “init --url” Generated Assets schema omits the output line, which contradicts the new default shown earlier and in .gitignore. Suggest adding it for consistency:

 generator client {
   provider = "prisma-client-js"
+  output   = "../generated/prisma"
 }

Please confirm that prisma init --url ... also emits the output field today; if not, we should add a short note explaining why this variant differs. (prisma.io)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eb89de2 and d5dd23e.

📒 Files selected for processing (1)

• content/200-orm/500-reference/200-prisma-cli-reference.mdx (1 hunks)

⏰ 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: runner / linkspector