feat: add mention of mongo support coming for P7 #7271
Conversation
Dangerous URL checkNo absolute URLs to prisma.io/docs found. |
WalkthroughThis PR removes mentions that Prisma Client is generated into Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes
Possibly related PRs
Pre-merge checks✅ Passed checks (3 passed)
Comment |
Redirect checkThis PR probably requires the following redirects to be added to static/_redirects:
|
Deploying docs with
|
| Latest commit: |
e0aeea7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://fd757909.docs-51g.pages.dev |
| Branch Preview URL: | https://mongo-db-dc-6226.docs-51g.pages.dev |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (13)
content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx(5 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx(9 hunks)content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx(2 hunks)content/200-orm/050-overview/500-databases/600-mongodb.mdx(1 hunks)content/250-postgres/100-introduction/225-import-from-existing-database.mdx(1 hunks)content/800-guides/050-migrate-from-mongoose.mdx(5 hunks)
💤 Files with no reviewable changes (7)
- content/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx
🧰 Additional context used
🧠 Learnings (8)
📓 Common learnings
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.
📚 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: 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".
Applied to files:
content/250-postgres/100-introduction/225-import-from-existing-database.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx
📚 Learning: 2025-10-08T16:22:57.129Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.
Applied to files:
content/200-orm/050-overview/500-databases/600-mongodb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/800-guides/050-migrate-from-mongoose.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/200-orm/050-overview/500-databases/600-mongodb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/800-guides/050-migrate-from-mongoose.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/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/800-guides/050-migrate-from-mongoose.mdx
📚 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/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/800-guides/050-migrate-from-mongoose.mdx
📚 Learning: 2025-10-15T06:36:42.423Z
Learnt from: jy-joung-bitor
Repo: prisma/docs PR: 0
File: :0-0
Timestamp: 2025-10-15T06:36:42.423Z
Learning: The `tsc --init` command requires the `--types node` flag to properly include Node.js type definitions from `types/node` in the generated tsconfig.json, even when types/node is already installed. Without this flag, TypeScript may not automatically pick up Node.js typings.
Applied to files:
content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx
📚 Learning: 2025-10-15T06:36:42.423Z
Learnt from: jy-joung-bitor
Repo: prisma/docs PR: 0
File: :0-0
Timestamp: 2025-10-15T06:36:42.423Z
Learning: The `npm init` command supports the `--init-type=module` flag to initialize a project with ES module type in package.json. This is a valid npm CLI option documented at https://docs.npmjs.com/cli/v11/commands/npm-init#init-type
Applied to files:
content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx
🪛 LanguageTool
content/200-orm/050-overview/500-databases/600-mongodb.mdx
[style] ~17-~17: ‘In the meantime’ might be wordy. Consider a shorter alternative.
Context: ... ORM v7 is coming in the near future.** In the meantime, please use Prisma ORM v6.19 (the l...
(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
[style] ~16-~16: ‘In the meantime’ might be wordy. Consider a shorter alternative.
Context: ... ORM v7 is coming in the near future.** In the meantime, please use Prisma ORM v6.19 (the l...
(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)
[style] ~160-~160: It’s more common nowadays to write this noun as one word.
Context: ...nents: - USERNAME: Your database user name - PASSWORD: Your database user pa...
(RECOMMENDED_COMPOUNDS)
content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx
[style] ~17-~17: ‘In the meantime’ might be wordy. Consider a shorter alternative.
Context: ... ORM v7 is coming in the near future.** In the meantime, please use Prisma ORM v6.19 (the l...
(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)
content/800-guides/050-migrate-from-mongoose.mdx
[style] ~17-~17: ‘In the meantime’ might be wordy. Consider a shorter alternative.
Context: ... ORM v7 is coming in the near future.** In the meantime, please use Prisma ORM v6.19 (the l...
(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)
⏰ 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: Cloudflare Pages
🔇 Additional comments (16)
content/250-postgres/100-introduction/225-import-from-existing-database.mdx (2)
1-9: Front matter and titles follow documentation standards.The YAML front matter is well-structured. All titles correctly use sentence case and properly preserve the "Prisma Postgres" product name casing, in alignment with documentation guidelines.
11-14: All referenced guides exist and links are correctly configured—no action required.The verification confirms both guides exist at:
content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdxcontent/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdxThe Docusaurus configuration automatically strips numeric prefixes from file paths when generating URLs (e.g.,
110-import-from-existing-database-postgresqlbecomesimport-from-existing-database-postgresql). The links in your file match the resulting URL structure exactly, so users will reach the correct pages without hitting 404s.content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx (1)
132-132: Dependency additions are appropriate for TypeScript/PostgreSQL setup.The additions of
pgand@types/pgare correctly placed:pgas a runtime dependency (needed by the adapter at runtime) and@types/pgas a dev dependency (TypeScript types for development). This aligns with the earlier introduction of@prisma/adapter-pgand ensures proper type support in the setup.Also applies to: 176-176, 184-186
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx (3)
55-56: Version pinning strategy ensures MongoDB compatibility.Exact pinning to v6.19 prevents accidental upgrades to v7 (even if released during a
npm installornpm updatelater). This is prudent given the v7 support is still forthcoming. The dependency separation (dev vs runtime) is correct.
213-227: db push explanation effectively clarifies MongoDB schema workflow.The updated description correctly distinguishes MongoDB's flexible schema from relational migration models and explicitly states that
db push"automatically regenerates Prisma Client." The info block further clarifies that no migration files are created, helping prevent confusion from developers familiar with Prisma's relational database workflows.
14-20: Update documentation with correct latest v6 version.The verification reveals a factual error: the document claims v6.19 is the latest v6 release, but the actual latest version on npm is 6.16.1 (as of November 17, 2025).
Update lines 14-20 and the corresponding section at lines 65-71 to reference v6.16.1 instead of v6.19. Version accuracy is critical in documentation—users relying on this guidance may attempt to install a version that doesn't exist or is outdated.
⛔ 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: 7157 File: content/800-guides/400-deno-integration.mdx:188-190 Timestamp: 2025-10-03T19:30:57.554Z Learning: For the prisma/docs repository, do not suggest changes to code blocks when reviewing documentation pull requests.Learnt from: aidankmcalister Repo: prisma/docs PR: 7165 File: content/800-guides/550-test-guide.mdx:50-66 Timestamp: 2025-10-08T16:22:57.129Z Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx (4)
15-47: v6.19 guidance is clear with helpful alternatives.The warning block combined with the info block creates a two-part explanation: (1) why v6.19 is needed right now, and (2) that users can alternatively use
@6for flexibility. This gives users agency while still recommending the tested v6.19 version. Good pedagogical approach.
108-112: Generation timing note prevents common confusion.The explicit note that Prisma Client is generated "later in this guide" helps users understand that
prisma initdoes not immediately generate the client. This clarity, combined with the consistentoutput = "../generated/prisma"path across the init command and schema, sets proper expectations for the workflow.
171-175: Connection string tip is practical and covers both hosting options.The tip concisely reminds users to replace placeholders and references both MongoDB Atlas and self-hosted deployments. This prevents the common mistake of using literal placeholder values as connection strings.
213-227: db push explanation clearly contrasts MongoDB and relational workflows.The explanation explicitly states that
db push"automatically generates Prisma Client," reinforcing the generation-first workflow. The info block further contextualizes why migrations aren't used for MongoDB, helping users understand the architectural differences. This approach prevents users from attempting to useprisma migratecommands on MongoDB.content/800-guides/050-migrate-from-mongoose.mdx (5)
47-62: Prisma dependency section clearly guides v6.19 adoption.The new section explicitly installs v6.19 and provides context via the info block about why this version is necessary. The flexible alternative (
prisma@6range) gives users options while emphasizing the v6.19 recommendation. This is well-structured for a migration guide.
304-312: "Generate Prisma Client" section accurately reflects the workflow.Renaming from "Install Prisma Client" to "Generate Prisma Client" and clarifying that the client is "created in the
generated/prismadirectory" removes ambiguity about the process. This aligns with the generation-first approach being emphasized across MongoDB documentation in this PR.
168-396: Schema examples and Mongoose-to-Prisma comparison are pedagogically sound.The tabbed comparison of Mongoose vs Prisma Client queries provides clear, side-by-side migration patterns. The Express controller example demonstrates real-world usage in context. These examples effectively guide developers through the mental model shift from Mongoose to Prisma, which is the core value of a migration guide.
15-31: Prerequisites section is accurate and properly versioned.The v7 MongoDB warning maintains consistency across the migration guides. The prerequisites are clear and well-informed—specifically, linking to Node.js version requirements ensures the guide stays current without needing manual updates for each release. The MongoDB 4.2+ requirement with replica set recommendation is sound; replica sets are essential for Prisma ORM's transaction support with nested writes. The referenced Node.js version documentation link exists and is correct.
64-148: Prisma configuration sections provide comprehensive setup guidance.The new "1.3" and "1.4" sections break down Prisma setup into clear, digestible steps. The ESM-first generator with custom output path and the separate config file explanation help Mongoose developers understand the tooling differences. The
engine: "classic"setting is the correct default for Prisma v6.19, and the dotenv loading in the config file is essential for development. The configuration shown is accurate and well-explained.content/200-orm/050-overview/500-databases/600-mongodb.mdx (1)
15-23: MongoDB v7 messaging and guide references are correct and will generate valid links.Both referenced guides exist and map correctly to the documented paths:
/getting-started/prisma-orm/quickstart/mongodb→content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx✓/getting-started/prisma-orm/add-to-existing-project/mongodb→content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx✓The warning block effectively guides users to v6.19 with working links to the relevant getting-started guides. No issues to address.
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
Show resolved
Hide resolved
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
Outdated
Show resolved
Hide resolved
…project/800-mongodb.mdx
ankur-arch
changed the title
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx (1)
152-170: Duplicate: MongoDB Atlas connection string guidance remains inaccurate—database name is optional, not mandatory.The tip on line 168 continues to misrepresent MongoDB Atlas requirements. The previous review flagged that:
- Database names in Atlas connection URIs are optional—not something that "must" be manually appended
- If omitted, you still include "/" before any options; Atlas SRV records set
authSource=adminautomaticallyDevelopers can either append the database name to the URL or specify it via connection options. Updating the tip to reflect this flexibility will prevent confusion:
- For MongoDB Atlas, you can manually append the database name to the connection URL, as Atlas doesn't include it by default. + For MongoDB Atlas, you can optionally append the database name to the connection URL, or specify it through connection options (e.g., authSource). Atlas SRV records automatically set authSource=admin.
🧹 Nitpick comments (2)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx (2)
16-16: Minor: Consider conciseness—"In the meantime" is slightly wordy."For now, please use..." or "Until then, use..." might be more direct alternatives.
160-164: Minor: Use compound "username" and "password" (single word) for consistency with standard terminology.
- "user name" → "username"
- "user password" → "password" (already correct)
Per static analysis, compound form is standard in contemporary technical writing.
- **`USERNAME`**: Your database user name - **`PASSWORD`**: Your database user password + **`USERNAME`**: Your database username + **`PASSWORD`**: Your database password
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx(9 hunks)
🧰 Additional context used
🧠 Learnings (5)
📓 Common learnings
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.
📚 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/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
📚 Learning: 2025-10-08T16:22:57.129Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.
Applied to files:
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.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: 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".
Applied to files:
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
📚 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/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
🪛 LanguageTool
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
[style] ~16-~16: ‘In the meantime’ might be wordy. Consider a shorter alternative.
Context: ... ORM v7 is coming in the near future.** In the meantime, please use Prisma ORM v6.19 (the l...
(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)
[style] ~160-~160: It’s more common nowadays to write this noun as one word.
Context: ...nents: - USERNAME: Your database user name - PASSWORD: Your database user pa...
(RECOMMENDED_COMPOUNDS)
⏰ 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). (1)
- GitHub Check: Cloudflare Pages
🔇 Additional comments (4)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx (4)
14-20: Approved: MongoDB v7 forthcoming warning is clear and directive.The warning accurately frames v7 support as coming soon while guiding users to v6.19 today. Tone and messaging are appropriate.
55-56: Approved: v6.19 version pinning is explicit and well-documented.Installation steps are precise, and the "Why Prisma v6.19?" info block clearly explains the MongoDB compatibility rationale. The fallback guidance to use
prisma@6for automatic updates is helpful.Also applies to: 65-71
190-205: Approved: Introspection and limitations guidance is thorough and realistic.The expanded description of
db pullbehavior and the dedicated limitations block set proper expectations for MongoDB schema inference. Noting that manual adjustments may be needed for relations, field types, and constraints is honest and helpful.
263-263: Approved: Schema evolution guidance now clearly explains MongoDB's approach.Reframing "Evolve your schema" to emphasize that MongoDB lacks traditional migrations and favors
db pushis accurate and user-friendly. The "Whydb pushinstead of migrations?" info block directly answers the likely question and reinforces the recommended workflow.Also applies to: 295-309
🍈 Lychee Link Check Report
📊 Results Overview
Errors per inputErrors in 200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx (1)
160-160: Fix compound word styling.Per standard English conventions, "user name" should be written as "username" (same for "user password" → "user password" is acceptable, but typically "password" in this context). For consistency with technical documentation, write "username" and "password" as single words in this components list.
Apply this diff:
- **`USERNAME`**: Your database user name - **`PASSWORD`**: Your database user password + **`USERNAME`**: Your database username + **`PASSWORD`**: Your database password
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx(5 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx(9 hunks)
💤 Files with no reviewable changes (2)
- content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdx
🧰 Additional context used
🧠 Learnings (6)
📓 Common learnings
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.
📚 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/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx
📚 Learning: 2025-10-08T16:22:57.129Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.
Applied to files:
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.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: 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".
Applied to files:
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx
📚 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/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.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/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx
🪛 LanguageTool
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
[style] ~16-~16: ‘In the meantime’ might be wordy. Consider a shorter alternative.
Context: ... ORM v7 is coming in the near future.** In the meantime, please use Prisma ORM v6.19 (the l...
(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)
[style] ~160-~160: It’s more common nowadays to write this noun as one word.
Context: ...nents: - USERNAME: Your database user name - PASSWORD: Your database user pa...
(RECOMMENDED_COMPOUNDS)
content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx
[style] ~17-~17: ‘In the meantime’ might be wordy. Consider a shorter alternative.
Context: ... ORM v7 is coming in the near future.** In the meantime, please use Prisma ORM v6.19 (the l...
(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)
⏰ 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: Cloudflare Pages
🔇 Additional comments (14)
content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx (7)
15-21: Clear v7 transition messaging and v6.19 recommendation.The warning box effectively communicates that MongoDB v7 support is forthcoming and establishes v6.19 as the current recommended version. This directly addresses the PR objective.
The only minor style note: LanguageTool suggests "In the meantime" (line 17) might be wordy—alternatives like "Until then" could be considered, though the current phrasing is appropriate for documentation tone.
37-47: Version pinning and explanation are well-structured.Specifying
prisma@6.19and@prisma/client@6.19(line 37–38) ensures users get the MongoDB-compatible release. The info box (lines 41–47) helpfully clarifies why v6.19 is used and explains theprisma@6escape hatch for users who want the latest v6 automatically. Well done.Please confirm that v6.19 is the current latest stable v6 release and that it is the correct version for full MongoDB support. If the version or recommendation changes, these lines will need updating.
99-99: Init command and Prisma Client generation flow are clearly documented.The
--output ../generated/prismaflag (line 99) and the accompanying note (lines 108–112) make it explicit that Prisma Client will be generated in a custom directory, which sets users up for success when they reach the import step later. The updated list of whatprisma initcreates (lines 104–106) correctly includesprisma.config.ts.Confirm that the
--outputflag is a valid option forprisma initin v6.19 and that theprisma.config.tsfile is correctly generated with that command.Also applies to: 104-112
171-175: Helpful tip for MongoDB Atlas integration.The tip at lines 171–175 clarifies what values must be replaced in the connection string and points users to MongoDB Atlas—important context for those unfamiliar with MongoDB connection strings.
213-227: MongoDB schema flexibility is well-explained.The rewritten guidance clarifies that MongoDB uses a flexible schema and that
db pushcreates collections without generating migration files (lines 219–221). The follow-up info box (lines 223–227) reinforces this distinction, which is crucial for users migrating from relational database quickstarts. Excellent.
233-240: Prisma Client import path is consistent with earlier guidance.The import from
../generated/prisma/client(line 235) correctly mirrors the output directory specified in the init step (line 99), ensuring the guide's path references are coherent throughout.
1-13: Metadata and component imports are appropriate.Frontmatter (lines 2–5) and component imports (lines 8–11) are well-structured for the MongoDB-specific quickstart.
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx (7)
14-20: Good addition — clarifies MongoDB support status and v6.19 guidance.The warning block clearly communicates the current state and directs users to the correct version. Consider addressing the wordiness note from static analysis on line 16: "In the meantime" could be shortened to "Until then" or "For now" for tighter prose.
55-56: Version pinning is correct and aligns with PR objective.The explicit
@6.19pins ensure users install the MongoDB-compatible release without ambiguity.
65-71: Clear explanation of version choice.The rationale helps users understand why v6.19 is pinned and gives them autonomy if they prefer auto-updating within v6.
78-78: Init command flags are correct.The
--outputflag is properly used and consistent with the generator output path defined later in the schema.
134-134: Explicit datasource URL is good practice.Makes the environment variable binding explicit and clearer for users configuring their first Prisma project.
190-205: Introspection section is clearer with expanded description and limitations.The bullet points on lines 190–195 make it explicit what
db pulldoes, and the new limitations block (lines 200–204) properly sets MongoDB-specific expectations and prevents user frustration. Good UX improvement.
261-309: Schema evolution section now correctly emphasizes MongoDB's flexible schema model.The reworded guidance (line 263) clearly states MongoDB doesn't support migrations, and the expanded db push explanation with the "Why db push?" info block (lines 305–309) properly educates users on MongoDB's schema model. This prevents frustration from users expecting traditional migration workflows.
* feat: add mention of mongo support coming for mongo * fix: refinements * Update content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
Summary by CodeRabbit