Include Prisma init commands for npm, yarn, and pnpm wihtout prisma+postgres

[sovetski]

Added instructions for initializing Prisma with different package managers without prisma+postgres

Summary by CodeRabbit

• Documentation
  • Added an alternative PostgreSQL initialization path for Prisma setup in the Turborepo guide with additional command examples.

[coderabbitai[bot]]

Walkthrough

Adds an alternative Prisma initialization pathway for PostgreSQL in the turborepo documentation guide. A new tabbed snippet section demonstrates initializing Prisma with the PostgreSQL datasource provider, presented as an optional approach following the standard Prisma setup step.

Changes

Cohort / File(s)	Change Summary
Turborepo Guide Documentation content/800-guides/080-turborepo.mdx	Adds alternative Prisma PostgreSQL initialization instructions with tabbed snippets for npm/yarn/pnpm commands using --datasource-provider postgresql flag; integrates new content block into existing Prisma setup section after initial initialization step

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Documentation additions are localized to a single file
• Changes consist of repetitive command snippet patterns across package managers (npm/yarn/pnpm)
• No complex logic, structural changes, or dependencies to evaluate

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title contains a typo ('wihtout' instead of 'without') and is partially related to the changeset—it mentions the package managers and Prisma init commands, but the actual change adds an alternative PostgreSQL initialization path, not commands 'without prisma+postgres'.	Correct the typo to 'without' and clarify whether the title should reflect 'alternative Prisma PostgreSQL initialization' or better describe the actual addition to the documentation.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e25a5a73526b6d5c64e7767ab23386a52287668a and 4308ac896953f5ceb06fbac1592364acc94e72ca.

📒 Files selected for processing (1)

• content/800-guides/080-turborepo.mdx (1 hunks)

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.

📚 Learning: 2025-10-09T21:32:50.340Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.

Applied to files:

• content/800-guides/080-turborepo.mdx

📚 Learning: 2025-08-11T09:40:55.237Z

Learnt from: ankur-arch
Repo: prisma/docs PR: 7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.

Applied to files:

• content/800-guides/080-turborepo.mdx

📚 Learning: 2025-10-08T16:23:00.388Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.

Applied to files:

• content/800-guides/080-turborepo.mdx

🔇 Additional comments (1)

content/800-guides/080-turborepo.mdx (1)

185-185: Clarify the distinction between Prisma Postgres and self-managed PostgreSQL initialization.

The phrasing "or you can skip prisma+postgres" is misleading. The first approach (--db, which is shorthand for --datasource-provider prisma+postgres) provisions Prisma Postgres—a managed DBaaS. The alternative (--datasource-provider postgresql) configures a self-managed PostgreSQL database. These are fundamentally different offerings, not variations where one "skips" a feature.

Additionally, the post-initialization documentation states "A Prisma Postgres database" is created, which is incorrect for users following the second approach.

Recommended fix: Replace the separator with clearer language like "Alternatively, initialize Prisma with a self-managed PostgreSQL database:" and split the post-initialization documentation (lines 215-221) to clarify what each approach provisions.

⛔ Skipped due to learnings

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".

---

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

[aidankmcalister]

Thank you for opening this PR, but we will not be merging this in. We would like to keep it consistent and promote the use of Prisma Postgres.

Although, we are open to adding an admonition to each guide mentioning that you can remove --db.

[aidankmcalister]

We've discussed this PR internally and have decided to move forward with it. We apologize for the initial rejection. I've left one comment for some text changes.

Thank you for opening this PR!

[sovetski]

We've discussed this PR internally and have decided to move forward with it. We apologize for the initial rejection. I've left one comment for some text changes.

Thank you for opening this PR!

@aidankmcalister thank you! I don't see your comment, did you submit it?