doc(prisma): add edge compatibility section #9965
Closed
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Ignored Deployments
|
github-actions
bot
added
adapters
ndom91
reviewed
Feb 8, 2024
Comment on lines
+182
to
+185
| * import { PrismaAdapter } from "@auth/prisma-adapter" | ||
| * | ||
| * export const { handlers, auth, signIn, signOut, unstable_update } = NextAuth({ | ||
| * adapter: PrismaAdapter(globalThis.prisma), |
There was a problem hiding this comment.
Suggested change
| * import { PrismaAdapter } from "@auth/prisma-adapter" | |
| * | |
| * export const { handlers, auth, signIn, signOut, unstable_update } = NextAuth({ | |
| * adapter: PrismaAdapter(globalThis.prisma), | |
| * import { PrismaAdapter } from "@auth/prisma-adapter" | |
| * import { PrismaClient } from "@prisma/client" | |
| * | |
| * globalThis.prisma ??= new PrismaClient() | |
| * | |
| * export const { handlers, auth, signIn, signOut, unstable_update } = NextAuth({ | |
| * adapter: PrismaAdapter(globalThis.prisma), |
ndom91
reviewed
Feb 8, 2024
Comment on lines
+162
to
+164
| * At the moment, Prisma is still working on being fully compatible with the Vercel edge runtime. See the issue being tracked [here](https://github.com/prisma/prisma/issues/20560). There are two options to deal with this issue: | ||
| * - Use the Prisma's [Accelerate plan](https://pris.ly/d/accelerate) | ||
| * - Switch to the `jwt` session strategy. Below is an example: |
There was a problem hiding this comment.
Suggested change
| * At the moment, Prisma is still working on being fully compatible with the Vercel edge runtime. See the issue being tracked [here](https://github.com/prisma/prisma/issues/20560). There are two options to deal with this issue: | |
| * - Use the Prisma's [Accelerate plan](https://pris.ly/d/accelerate) | |
| * - Switch to the `jwt` session strategy. Below is an example: | |
| * At the moment, Prisma is still working on being fully compatible with the Vercel edge runtime. See the issue being tracked [here](https://github.com/prisma/prisma/issues/20560), and Prisma’s announcement about edge support in early access since 5.9.0 [here](https://github.com/prisma/prisma/releases/tag/5.9.0). There are two options to deal with this issue: | |
| * | |
| * - Use the Prisma’s [Accelerate](https://pris.ly/d/accelerate) feature | |
| * - Switch to the `jwt` session strategy | |
| * | |
| * Using Prisma in and edge runtime with `jwt` session strategy looks like this. |
|
Small tweaks otherwise lgtm! |
|
Shouldn't be necessary for Prisma v5.9.1 or higher anymore |
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.
Add the edge compat section for Prisma