Update ORM docs #7253
Closed
Update ORM docs #7253
Conversation
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
Contributor
Dangerous URL checkNo absolute URLs to prisma.io/docs found. |
Contributor
WalkthroughThis PR updates 70+ documentation MDX files: it changes Prisma generator blocks from provider = "prisma-client-js" to provider = "prisma-client" and adds explicit generator outputs (output = "./generated"), updates PrismaClient import paths to the generated client locations, and removes or moves datasource URL/directUrl/shadowDatabaseUrl lines (introducing prisma.config.ts examples in some places). One adapter class rename (PrismaBetterSQLite3 → PrismaBetterSqlite3) is also applied in docs. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes
Possibly related PRs
Pre-merge checks❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (2)
🧰 Additional context used🧠 Learnings (6)📓 Common learnings📚 Learning: 2025-10-08T16:23:00.388ZApplied to files:
📚 Learning: 2025-10-03T19:30:57.554ZApplied to files:
📚 Learning: 2025-10-08T16:22:57.129ZApplied to files:
📚 Learning: 2025-10-09T21:32:50.340ZApplied to files:
📚 Learning: 2025-08-11T09:40:55.237ZApplied to files:
⏰ 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). (4)
🔇 Additional comments (3)
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. Comment |
Contributor
Redirect checkThis PR probably requires the following redirects to be added to static/_redirects:
|
Contributor
🍈 Lychee Link Check Report
📊 Results Overview
|
Deploying docs with
|
| Latest commit: |
e9261ed
|
| Status: | 🚫 Build failed. |
![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: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (7)
content/200-orm/050-overview/500-databases/900-turso.mdx (2)
115-115: Typo in code fence directive.Line 115 contains a typo: the code fence specifies
terminainstead ofterminal.Apply this diff to fix the typo:
-```termina +```terminal
84-103: Fix typo on line 115 and add brief schema context for the generated client import path.Line 115 contains a typo in the code fence:
terminashould beterminal.Additionally, line 95's import path
../prisma/generated/clientassumes the Prisma Client is generated to a custom location. While this pattern is documented in the database-drivers guide, the Turso guide would benefit from a brief note referencing the required schema configuration. Either add a link to the database-drivers documentation explaining custom output paths, or include a concise schema snippet showing:generator client { provider = "prisma-client" output = "./generated" }This ensures readers understand how to configure their schema to match the import path shown in your code example.
content/200-orm/050-overview/500-databases/200-database-drivers.mdx (1)
123-123: Update import path on line 123 to match the documented pattern.The inconsistency is confirmed. Line 123 uses
'../prisma/prisma-client'while lines 105 and 140 both use'../prisma/generated/client'. Prisma 6.6.0 introduced a new prisma-client generator requiring explicit output paths, with imports from the custom output folder. For consistency and clarity throughout the documentation, line 123 should be updated:- import { PrismaClient } from '../prisma/prisma-client' + import { PrismaClient } from '../prisma/generated/client'content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx (1)
200-229: Inconsistent PrismaClient import between TypeScript and JavaScript examples.Line 229 shows the JavaScript seed example importing from
@prisma/client, but the schema block directly above (lines 200-203) defines the new generator configuration withprovider = "prisma-client"andoutput = "./generated". The TypeScript example (line 103) correctly imports from../prisma/generated/client.For consistency and to accurately reflect the updated pattern, the JavaScript import should mirror the TypeScript approach:
-const { PrismaClient } = require('@prisma/client') +const { PrismaClient } = require('../prisma/generated/client')This mixed pattern could confuse readers about whether they should use the generated client or the public package.
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx (1)
196-287: Critical: Import paths are incorrect relative to file location.The schema at lines 196–199 shows
output = "./generated"(at project root), but the import at line 274 inapp/api/edge/route.tsusesfrom './generated/client'. This resolves toapp/api/edge/generated/clientwhich doesn't exist.The correct import from
app/api/edge/route.tsto a root-levelgenerated/clientshould be:-import { PrismaClient } from './generated/client' +import { PrismaClient } from '../../../generated/client'This same error appears in subsequent database examples (Vercel Postgres, PlanetScale, Neon sections) at lines 407, 539, and 590.
Incorrect relative paths will cause import failures in deployed code. All four occurrences need correction.
content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx (1)
36-45: Fix minor typos.
- “the the number” → “the number”
- “If you have one application instances” → “If you have one application instance”
-`num_physical_cpus` refers to the the number of CPUs... +`num_physical_cpus` refers to the number of CPUs... -If you have **one** application instances: +If you have **one** application instance:content/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx (1)
157-175: Clarify guidance forprisma-clientvsprisma-client-jsimports.This section describes
@prisma/clientbut the page demonstratesprisma-clientwith custom output. Clarify both cases and ensure the example matches.-The `@prisma/client` npm package consists of two key parts: +If you use the legacy `prisma-client-js` generator, the `@prisma/client` npm package consists of two key parts: ... -This means that you still import `@prisma/client` in your own `.ts` files: -```ts -import { PrismaClient } from '../prisma/generated/client' -``` +With `prisma-client-js`, you import from `@prisma/client`. With the newer `prisma-client`, you import from your configured `output` path (e.g., `./generated/client`). +```ts +// prisma-client-js +import { PrismaClient } from '@prisma/client' +// prisma-client +import { PrismaClient } from './generated/client' +```
🧹 Nitpick comments (9)
content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/index.mdx (1)
80-117: Consider adding a contextual note about the generator setup.While the import paths are now correct for the new configuration, readers unfamiliar with the prisma.config.ts changes might benefit from a brief callout explaining why this import path is used. You could add a small admonition or cross-reference linking to the generator configuration section.
content/200-orm/050-overview/500-databases/400-mysql.mdx (1)
68-68: Ensure import statement is shown for driver adapter example.Line 68 shows the PrismaClient instantiation but should also show the import statement at the top to be complete. Consider adding:
import { PrismaMariaDb } from '@prisma/adapter-mariadb'; import { PrismaClient } from './generated/prisma';This ensures readers have a complete, copy-paste-ready code example.
content/200-orm/100-prisma-schema/20-data-model/80-table-inheritance.mdx (1)
144-148: Clarify the import source change from @prisma/client to generated client.The imports have been updated from
@prisma/clientto../prisma/generated/client, but there's no explanation for why users should import from the generated output directory rather than the standard npm package. This represents a significant shift in recommended practice. Consider adding a brief note explaining when/why developers should prefer the generated client path, or ensure this is explained in a related guide on generator configuration.content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx (1)
385-385: Import path change lacks explanation in context.Similar to the table-inheritance.mdx file, the import source has been updated from
@prisma/clientto../prisma/generated/client. As this represents a shift from importing from the npm package to a relative generated path, consider adding a note or linking to documentation that explains this pattern change.content/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx (1)
165-165: Wording improvement opportunity.Line 165 reads: "you need to manually re-generate Prisma Client to update the generated code". Consider strengthening this to remove the redundancy: "you need to regenerate Prisma Client to update the generated code in your output directory" or simply "you need to run
prisma generateto update your output directory."content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx (1)
64-69: Align generator output with import path for consistency.Imports use ../prisma/generated/client, but the generator block outputs to ../src/generated/prisma. Pick one. Suggest standardizing on ../prisma/generated/client here to match all imports.
Apply this diff to the generator block:
generator client { - provider = "prisma-client" - output = "../src/generated/prisma" + provider = "prisma-client" + output = "../prisma/generated/client" engineType = "client" // no Rust engine }Also applies to: 96-104, 225-233, 275-280
content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx (1)
157-175: Update the “@prisma/client” section to match prisma-client generator usage.This section says to “still import @prisma/client” but the example imports from a generated path. For prisma-client, users import from the configured output; @prisma/client text belongs to prisma-client-js.
-This means that you still import `@prisma/client` in your own `.ts` files: - -```ts -import { PrismaClient } from '../prisma/generated/client' -``` +With the `prisma-client` generator, import from your configured output path (example above: `./generated/client`). If you use the legacy `prisma-client-js`, you import from `@prisma/client`. + +```ts +import { PrismaClient } from './generated/client' +```content/200-orm/500-reference/100-prisma-schema-reference.mdx (1)
171-179: Move/removemoduleFormatfrom the prisma-client-js fields table.The row says it’s “available only with
prisma-clientgenerator” but appears under theprisma-client-jstable, which is confusing.-| `moduleFormat` | No | Enum (`cjs` or `esm`) | Defines the module format of the generated Prisma Client. This field is available only with `prisma-client` generator. |Move this row into the “Fields for
prisma-clientprovider” table below (or delete here if already documented there).content/200-orm/800-more/350-ai-tools/100-cursor.mdx (1)
206-213: Make the seed import match the generator output.The generator outputs to ./generated, but the seed script imports from ../prisma/generated/client. Align these.
-} from "../prisma/generated/client"; +} from "./generated/client";Also applies to: 339-345
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (90)
content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx(5 hunks)content/200-orm/050-overview/100-introduction/300-data-modeling.mdx(1 hunks)content/200-orm/050-overview/300-prisma-in-your-stack/01-rest.mdx(1 hunks)content/200-orm/050-overview/300-prisma-in-your-stack/03-fullstack.mdx(1 hunks)content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx(4 hunks)content/200-orm/050-overview/500-databases/200-database-drivers.mdx(4 hunks)content/200-orm/050-overview/500-databases/300-postgresql.mdx(2 hunks)content/200-orm/050-overview/500-databases/400-mysql.mdx(1 hunks)content/200-orm/050-overview/500-databases/500-sqlite.mdx(2 hunks)content/200-orm/050-overview/500-databases/800-sql-server/index.mdx(2 hunks)content/200-orm/050-overview/500-databases/840-cockroachdb.mdx(1 hunks)content/200-orm/050-overview/500-databases/850-planetscale.mdx(2 hunks)content/200-orm/050-overview/500-databases/880-supabase.mdx(0 hunks)content/200-orm/050-overview/500-databases/890-neon.mdx(1 hunks)content/200-orm/050-overview/500-databases/900-turso.mdx(1 hunks)content/200-orm/050-overview/600-beyond-prisma-orm.mdx(1 hunks)content/200-orm/100-prisma-schema/10-overview/index.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/10-models.mdx(2 hunks)content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx(2 hunks)content/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdx(0 hunks)content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/40-views.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/65-externally-managed-tables.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/80-table-inheritance.mdx(3 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx(2 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx(5 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/015-instantiate-prisma-client.mdx(2 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/100-connection-management.mdx(1 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx(3 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx(4 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/200-read-replicas.mdx(1 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx(12 hunks)content/200-orm/200-prisma-client/100-queries/030-crud.mdx(2 hunks)content/200-orm/200-prisma-client/100-queries/037-relation-queries.mdx(1 hunks)content/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdx(1 hunks)content/200-orm/200-prisma-client/100-queries/058-transactions.mdx(3 hunks)content/200-orm/200-prisma-client/100-queries/060-full-text-search.mdx(2 hunks)content/200-orm/200-prisma-client/100-queries/061-custom-validation.mdx(2 hunks)content/200-orm/200-prisma-client/100-queries/062-computed-fields.mdx(2 hunks)content/200-orm/200-prisma-client/100-queries/064-custom-models.mdx(2 hunks)content/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdx(1 hunks)content/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdx(1 hunks)content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx(1 hunks)content/200-orm/200-prisma-client/400-type-safety/830-prisma-type-system.mdx(0 hunks)content/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdx(1 hunks)content/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdx(1 hunks)content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx(8 hunks)content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx(9 hunks)content/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdx(2 hunks)content/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdx(3 hunks)content/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdx(3 hunks)content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx(1 hunks)content/200-orm/300-prisma-migrate/050-getting-started.mdx(0 hunks)content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdx(0 hunks)content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx(2 hunks)content/200-orm/300-prisma-migrate/300-workflows/110-native-database-types.mdx(0 hunks)content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx(1 hunks)content/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdx(2 hunks)content/200-orm/500-reference/050-prisma-client-reference.mdx(13 hunks)content/200-orm/500-reference/100-prisma-schema-reference.mdx(3 hunks)content/200-orm/500-reference/200-prisma-cli-reference.mdx(11 hunks)content/200-orm/500-reference/380-connection-urls.mdx(0 hunks)content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx(1 hunks)content/200-orm/800-more/100-under-the-hood/100-engines.mdx(2 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/500-upgrading-to-prisma-6.mdx(9 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/001-rejectonnotfound-changes.mdx(1 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/101-jsonprotocol-changes.mdx(2 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdx(3 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/150-referential-actions.mdx(2 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/index.mdx(3 hunks)content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdx(1 hunks)content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdx(1 hunks)content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/04-upgrading-nexus-prisma-to-nexus.mdx(2 hunks)content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx(1 hunks)content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/06-upgrading-prisma-binding-to-sdl-first.mdx(1 hunks)content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/07-upgrading-a-rest-api.mdx(1 hunks)content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/08-upgrade-from-mongodb-beta.mdx(2 hunks)content/200-orm/800-more/350-ai-tools/100-cursor.mdx(2 hunks)content/200-orm/800-more/350-ai-tools/200-tabnine.mdx(3 hunks)content/200-orm/800-more/350-ai-tools/300-windsurf.mdx(2 hunks)content/200-orm/800-more/350-ai-tools/400-github-copilot.mdx(1 hunks)content/200-orm/800-more/600-help-and-troubleshooting/100-autocompletion-in-graphql-resolvers-with-js.mdx(2 hunks)content/200-orm/800-more/600-help-and-troubleshooting/300-implicit-to-explicit-conversion.mdx(1 hunks)content/200-orm/800-more/600-help-and-troubleshooting/400-nextjs-help.mdx(2 hunks)content/200-orm/800-more/600-help-and-troubleshooting/500-comparing-columns-through-raw-queries.mdx(6 hunks)content/200-orm/800-more/600-help-and-troubleshooting/800-check-constraints.mdx(5 hunks)content/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdx(5 hunks)content/200-orm/800-more/600-help-and-troubleshooting/950-typescript-performance-optimization.mdx(2 hunks)
💤 Files with no reviewable changes (7)
- content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdx
- content/200-orm/300-prisma-migrate/300-workflows/110-native-database-types.mdx
- content/200-orm/200-prisma-client/400-type-safety/830-prisma-type-system.mdx
- content/200-orm/300-prisma-migrate/050-getting-started.mdx
- content/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdx
- content/200-orm/500-reference/380-connection-urls.mdx
- content/200-orm/050-overview/500-databases/880-supabase.mdx
🧰 Additional context used
🧠 Learnings (5)
📚 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/200-orm/050-overview/100-introduction/300-data-modeling.mdxcontent/200-orm/050-overview/500-databases/850-planetscale.mdxcontent/200-orm/800-more/350-ai-tools/100-cursor.mdxcontent/200-orm/050-overview/500-databases/800-sql-server/index.mdxcontent/200-orm/050-overview/500-databases/300-postgresql.mdxcontent/200-orm/050-overview/100-introduction/100-what-is-prisma.mdxcontent/200-orm/050-overview/500-databases/900-turso.mdxcontent/200-orm/500-reference/200-prisma-cli-reference.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdxcontent/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdxcontent/200-orm/500-reference/050-prisma-client-reference.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/200-prisma-client/100-queries/061-custom-validation.mdxcontent/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdxcontent/200-orm/200-prisma-client/100-queries/030-crud.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/100-introduction/300-data-modeling.mdxcontent/200-orm/050-overview/500-databases/850-planetscale.mdxcontent/200-orm/800-more/350-ai-tools/100-cursor.mdxcontent/200-orm/050-overview/500-databases/800-sql-server/index.mdxcontent/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdxcontent/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdxcontent/200-orm/100-prisma-schema/20-data-model/10-models.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/200-orm/050-overview/500-databases/300-postgresql.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdxcontent/200-orm/050-overview/100-introduction/100-what-is-prisma.mdxcontent/200-orm/500-reference/200-prisma-cli-reference.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdxcontent/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdxcontent/200-orm/500-reference/050-prisma-client-reference.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/500-comparing-columns-through-raw-queries.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdxcontent/200-orm/050-overview/500-databases/890-neon.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/100-connection-management.mdxcontent/200-orm/200-prisma-client/100-queries/061-custom-validation.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/800-check-constraints.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/08-upgrade-from-mongodb-beta.mdxcontent/200-orm/100-prisma-schema/20-data-model/30-indexes.mdxcontent/200-orm/800-more/350-ai-tools/300-windsurf.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/300-implicit-to-explicit-conversion.mdxcontent/200-orm/100-prisma-schema/10-overview/index.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdxcontent/200-orm/050-overview/500-databases/400-mysql.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/500-upgrading-to-prisma-6.mdxcontent/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdxcontent/200-orm/200-prisma-client/100-queries/030-crud.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/100-introduction/300-data-modeling.mdxcontent/200-orm/050-overview/500-databases/850-planetscale.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/150-referential-actions.mdxcontent/200-orm/800-more/350-ai-tools/100-cursor.mdxcontent/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/950-typescript-performance-optimization.mdxcontent/200-orm/050-overview/500-databases/800-sql-server/index.mdxcontent/200-orm/800-more/350-ai-tools/400-github-copilot.mdxcontent/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdxcontent/200-orm/200-prisma-client/100-queries/062-computed-fields.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/06-upgrading-prisma-binding-to-sdl-first.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdxcontent/200-orm/050-overview/500-databases/900-turso.mdxcontent/200-orm/500-reference/200-prisma-cli-reference.mdxcontent/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/001-rejectonnotfound-changes.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/500-comparing-columns-through-raw-queries.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/400-nextjs-help.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/index.mdxcontent/200-orm/200-prisma-client/100-queries/061-custom-validation.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/800-check-constraints.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/08-upgrade-from-mongodb-beta.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/200-read-replicas.mdxcontent/200-orm/100-prisma-schema/20-data-model/30-indexes.mdxcontent/200-orm/200-prisma-client/100-queries/058-transactions.mdxcontent/200-orm/800-more/350-ai-tools/300-windsurf.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/300-implicit-to-explicit-conversion.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/500-upgrading-to-prisma-6.mdxcontent/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdxcontent/200-orm/200-prisma-client/100-queries/030-crud.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/200-orm/050-overview/100-introduction/300-data-modeling.mdxcontent/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdxcontent/200-orm/050-overview/500-databases/500-sqlite.mdxcontent/200-orm/050-overview/500-databases/850-planetscale.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/07-upgrading-a-rest-api.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/101-jsonprotocol-changes.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdxcontent/200-orm/800-more/350-ai-tools/100-cursor.mdxcontent/200-orm/050-overview/500-databases/800-sql-server/index.mdxcontent/200-orm/800-more/350-ai-tools/400-github-copilot.mdxcontent/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdxcontent/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdxcontent/200-orm/200-prisma-client/100-queries/062-computed-fields.mdxcontent/200-orm/200-prisma-client/100-queries/037-relation-queries.mdxcontent/200-orm/100-prisma-schema/20-data-model/10-models.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/200-orm/050-overview/500-databases/300-postgresql.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdxcontent/200-orm/050-overview/100-introduction/100-what-is-prisma.mdxcontent/200-orm/050-overview/500-databases/900-turso.mdxcontent/200-orm/500-reference/200-prisma-cli-reference.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/100-autocompletion-in-graphql-resolvers-with-js.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdxcontent/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdxcontent/200-orm/800-more/100-under-the-hood/100-engines.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdxcontent/200-orm/200-prisma-client/100-queries/060-full-text-search.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdxcontent/200-orm/500-reference/050-prisma-client-reference.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdxcontent/200-orm/100-prisma-schema/20-data-model/65-externally-managed-tables.mdxcontent/200-orm/200-prisma-client/100-queries/064-custom-models.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/200-orm/100-prisma-schema/20-data-model/40-views.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/400-nextjs-help.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdxcontent/200-orm/050-overview/500-databases/890-neon.mdxcontent/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdxcontent/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdxcontent/200-orm/200-prisma-client/100-queries/061-custom-validation.mdxcontent/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdxcontent/200-orm/800-more/350-ai-tools/200-tabnine.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/800-check-constraints.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/08-upgrade-from-mongodb-beta.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdxcontent/200-orm/050-overview/500-databases/840-cockroachdb.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/01-rest.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/200-read-replicas.mdxcontent/200-orm/100-prisma-schema/20-data-model/30-indexes.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/04-upgrading-nexus-prisma-to-nexus.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdxcontent/200-orm/800-more/350-ai-tools/300-windsurf.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/03-fullstack.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdxcontent/200-orm/100-prisma-schema/10-overview/index.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdxcontent/200-orm/050-overview/500-databases/400-mysql.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/500-upgrading-to-prisma-6.mdxcontent/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdxcontent/200-orm/200-prisma-client/100-queries/030-crud.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/200-orm/050-overview/500-databases/850-planetscale.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/101-jsonprotocol-changes.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdxcontent/200-orm/050-overview/500-databases/800-sql-server/index.mdxcontent/200-orm/800-more/350-ai-tools/400-github-copilot.mdxcontent/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/06-upgrading-prisma-binding-to-sdl-first.mdxcontent/200-orm/200-prisma-client/100-queries/037-relation-queries.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/200-orm/050-overview/500-databases/300-postgresql.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdxcontent/200-orm/500-reference/200-prisma-cli-reference.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdxcontent/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdxcontent/200-orm/800-more/100-under-the-hood/100-engines.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdxcontent/200-orm/200-prisma-client/100-queries/060-full-text-search.mdxcontent/200-orm/500-reference/050-prisma-client-reference.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/500-comparing-columns-through-raw-queries.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/200-orm/100-prisma-schema/20-data-model/40-views.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/400-nextjs-help.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdxcontent/200-orm/050-overview/600-beyond-prisma-orm.mdxcontent/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdxcontent/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdxcontent/200-orm/800-more/600-help-and-troubleshooting/800-check-constraints.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdxcontent/200-orm/050-overview/500-databases/840-cockroachdb.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/01-rest.mdxcontent/200-orm/100-prisma-schema/20-data-model/30-indexes.mdxcontent/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/500-upgrading-to-prisma-6.mdxcontent/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdx
🪛 LanguageTool
content/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx
[style] ~165-~165: Consider shortening or rephrasing this to strengthen your wording.
Context: ...Evolving your application Whenever you make changes to your database that are reflected in the...
(MAKE_CHANGES)
⏰ 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). (3)
- GitHub Check: runner / linkspector
- GitHub Check: Check internal links
- GitHub Check: Cloudflare Pages
...-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx
Show resolved
Hide resolved
Comment on lines
160
to
172
| ```js | ||
| import { Decimal, NotFoundError } from '@prisma/client/runtime' | ||
| import { Decimal, NotFoundError } from '../prisma/generated/client/runtime' | ||
| const num = new Decimal(24.454545) | ||
| const notFound = new NotFoundError() | ||
| ``` | ||
|
|
||
| will need to be changed to | ||
|
|
||
| ```js | ||
| import { Prisma } from '@prisma/client' | ||
| import { Prisma } from '../prisma/generated/client' | ||
| const num = new Prisma.Decimal(24.454545) | ||
| const notFound = new Prisma.NotFoundError() | ||
| ``` |
Contributor
There was a problem hiding this comment.
Align the before-code example with the text explanation.
The text at line 158 states: "Importing from @prisma/client/runtime is no longer available in Prisma ORM 5." However, the before-code example at line 161 shows:
import { Decimal, NotFoundError } from '../prisma/generated/client/runtime'This imports from a generated path, not from @prisma/client/runtime. For readers to understand the breaking change clearly, the before code should show the actual deprecated import path that users were using:
import { Decimal, NotFoundError } from '@prisma/client/runtime'This will make the migration path explicit: from the public @prisma/client/runtime to the new pattern using Prisma namespace from the generated client.
Apply this diff to correct the example:
#### Using public APIs from `@prisma/client/runtime`
Importing from `@prisma/client/runtime` is no longer available in Prisma ORM 5. If you were using public APIs available in this namespace before, you can instead import `Prisma` and access them. For example:
```js
-import { Decimal, NotFoundError } from '../prisma/generated/client/runtime'
+import { Decimal, NotFoundError } from '@prisma/client/runtime'
const num = new Decimal(24.454545)
const notFound = new NotFoundError()
<details>
<summary>🤖 Prompt for AI Agents</summary>
In
content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdx
around lines 160 to 172, the "before" example imports from a generated relative
path instead of the deprecated public package; replace the import line so it
shows the actual deprecated usage by importing Decimal and NotFoundError from
'@prisma/client/runtime' (keeping the subsequent lines the same) so the
migration example matches the explanatory text.
</details>
<!-- This is an auto-generated reply by CodeRabbit -->
Contributor
There was a problem hiding this comment.
@AmanVarshney01 is this how the import actually works? 👁️
Contributor
There was a problem hiding this comment.
Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!
Contributor
Author
There was a problem hiding this comment.
these are upgrading guides i am removing all the changes i did in this folder
Contributor
🍈 Lychee Link Check Report
📊 Results Overview
|
Contributor
🍈 Lychee Link Check Report
📊 Results Overview
Errors per inputErrors in 100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-mysql.mdx
Errors in 100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-planetscale.mdx
Errors in 100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-mysql.mdx
Errors in 100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx
Errors in 100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-mysql.mdx
Errors in 100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-planetscale.mdx
Errors in 100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-mysql.mdx
Errors in 100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx
Errors in 200-orm/050-overview/500-databases/400-mysql.mdx
Errors in 200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx
Errors in 200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdxErrors in 200-orm/100-prisma-schema/20-data-model/30-indexes.mdx
Errors in 200-orm/100-prisma-schema/20-data-model/40-views.mdx
Errors in 200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdx
Errors in 200-orm/200-prisma-client/100-queries/058-transactions.mdx
Errors in 200-orm/200-prisma-client/100-queries/060-full-text-search.mdx
Errors in 200-orm/200-prisma-client/100-queries/070-case-sensitivity.mdx
Errors in 200-orm/200-prisma-client/150-using-raw-sql/200-raw-queries.mdx
Errors in 200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx
Errors in 200-orm/300-prisma-migrate/050-getting-started.mdx
Errors in 200-orm/300-prisma-migrate/300-workflows/90-development-and-production.mdx
Errors in 200-orm/500-reference/100-prisma-schema-reference.mdx
Errors in 200-orm/500-reference/350-database-features.mdx
Errors in 200-orm/800-more/600-help-and-troubleshooting/050-dataguide/02-introduction-to-data-types.mdx
|
ankur-arch
reviewed
Nov 15, 2025
Comment on lines
+44
to
+48
| <Admonition type="info"> | ||
|
|
||
| **Note**: When using Prisma CLI commands, environment variables are not automatically loaded. You'll need to use a package like `dotenv` to load environment variables from a `.env` file, or ensure your environment variables are set in your shell. | ||
|
|
||
| </Admonition> |
Contributor
There was a problem hiding this comment.
Suggested change
| <Admonition type="info"> | |
| **Note**: When using Prisma CLI commands, environment variables are not automatically loaded. You'll need to use a package like `dotenv` to load environment variables from a `.env` file, or ensure your environment variables are set in your shell. | |
| </Admonition> | |
| :::info | |
| When using Prisma CLI commands, environment variables are not automatically loaded. You'll need to use a package like `dotenv` to load environment variables from a `.env` file, or ensure your environment variables are set in your shell. | |
| ::: |
@AmanVarshney01 can you update the components to use the more modern components while making changes in the PR?
ankur-arch
reviewed
Nov 15, 2025
| The database connection URL is configured in `prisma.config.ts`: | ||
|
|
||
| ```ts file=prisma.config.ts | ||
| import { defineConfig, env } from 'prisma/config' |
Contributor
There was a problem hiding this comment.
Suggested change
| import { defineConfig, env } from 'prisma/config' | |
| import 'dotenv/config' | |
| import { defineConfig, env } from 'prisma/config' |
@AmanVarshney01 let's add the import 'dotenv/config' to all the config files.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary by CodeRabbit
New Features
Bug Fixes
Documentation