upgrade docs to v6 #6445
upgrade docs to v6 #6445
Conversation
Dangerous URL checkNo absolute URLs to prisma.io/docs found. |
Redirect checkThis PR probably requires the following redirects to be added to static/_redirects:
|
Deploying docs with
|
| Latest commit: |
b825de5
|
| Status: | 🚫 Build failed. |
| @@ -18,7 +18,7 @@ If you want to use Prisma ORM with your own PostgreSQL, MySQL, MongoDB or any ot | |||
|
|
|||
| ## Prerequisites | |||
|
|
|||
| You need Node.js v16.13.0 or higher for this guide (learn more about [system requirements](/orm/reference/system-requirements)). | |||
| You need Node.js 18.18.0 / 20.9.0 / 22.11.0 or higher for this guide (learn more about [system requirements](/orm/reference/system-requirements)). | |||
There was a problem hiding this comment.
Isn't mention the minimum required version enough 👁️ ?
| You need Node.js 18.18.0 / 20.9.0 / 22.11.0 or higher for this guide (learn more about [system requirements](/orm/reference/system-requirements)). | |
| You need Node.js 18.18.0 or higher for this guide (learn more about [system requirements](/orm/reference/system-requirements)). |
Same suggestion applies for the one above.
There was a problem hiding this comment.
Afaiu the answer is actually no because e.g. a version like 19.0 or 20.1. wouldn't be supported, see here:
But I think you have a point that this may be confusing, I'll think about how to make this clearer 👍
| - Node.js v16.13.0 or higher (learn more about [system requirements](/orm/reference/system-requirements)) | ||
|
|
||
| > See [System requirements](/orm/reference/system-requirements) for exact version requirements. | ||
| - [Node.js](https://nodejs.org/en/) installed on your machine |
There was a problem hiding this comment.
Which version of node.js?
| @@ -64,7 +64,7 @@ npm install prisma@latest --save-dev | |||
| npm install @prisma/client@latest --save | |||
| ``` | |||
|
|
|||
| ### Step 2: Enable the feature flag in the Prisma schema file | |||
| ### 2. Enable the feature flag in the Prisma schema file | |||
There was a problem hiding this comment.
I like the numbering instead of the step 1/step 2-- it's more consistent with the rest of our docs.
|
|
||
| </TabItem> | ||
|
|
||
| <TabItem value="pnpm"> |
There was a problem hiding this comment.
Maybe also add bun @nikolasburk ?
...ent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/500-upgrading-to-prisma-6.mdx
Outdated
Show resolved
Hide resolved
| ### `tracing` | ||
|
|
||
| If you use the [OpenTelemetry tracing](/orm/prisma-client/observability-and-logging/opentelemetry-tracing#about-tracing) in your app, you can now remove `tracing` from the `previewFeatures` in your Prisma schema: | ||
|
|
||
| ```prisma | ||
| generator client { | ||
| provider = "prisma-client-js" | ||
| // delete-next-line | ||
| previewFeatures = ["tracing"] | ||
| } | ||
| ``` |
There was a problem hiding this comment.
tentative, probably won't make it
…ions/500-upgrading-to-prisma-6.mdx Co-authored-by: Alexey Orlenko <[email protected]>
Resolves DA-1712