chore(docs): improve edge compatibility (#11061)

Author: ThangHuuVu

docs/pages/getting-started/adapters/prisma.mdx

@@ -103,54 +103,12 @@ The original database edge-runtime workaround, to split your `auth.ts` configura
 At the moment, Prisma is still working on being fully compatible with edge runtimes like Vercel's. See the issue being tracked [here](https://github.com/prisma/prisma/issues/20560), and Prisma's announcement about early edge support in the `5.9.1` [changelog](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
+- Follow our [Edge Compatibility](/guides/edge-compatibility) page as the workaround. This uses the `jwt` session strategy and separates the `auth.ts` configuration into two files.
 
 Using Prisma with the `jwt` session strategy and `@prisma/[email protected]` or above doesn't require any additional modifications, other than ensuring you don't do any database queries in your middleware.
 
 Since `@prisma/[email protected]`, Prisma no longer throws about being incompatible with the edge runtime at instantiation, but at query time. Therefore, it is possible to import it in files being used in your middleware as long as you do not execute any queries in your middleware.
 
-<Accordions>
-<Accordion title="Using '@prisma/client' before 'v5.9.1' requires some additional workarounds">
-
-You will need to separate your Auth.js configuration into two files and use the [lazy initialization](/reference/next-auth#lazy-initialization) feature to instantiate a second copy of Auth.js in the middleware without the adapter.
-
-Define the `auth.config.ts` file:
-
-```ts filename="auth.config.ts"
-export default {
-  providers: [GitHub, Google, Facebook, Twitter],
-} satisfies NextAuthConfig
-```
-
-Import and use the `PrismaAdapter` in the `auth.ts` file. This is your main Auth.js configuration file that you'll use around the rest of your application.
-
-```ts filename="auth.ts"
-import NextAuth from "next-auth"
-import authConfig from "./auth.config"
-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),
-  session: { strategy: "jwt" },
-  ...authConfig,
-})
-```
-
-In the middleware file, however, import the first `auth.config` and instantiate a second instance of `NextAuth` using it as the configuration (note that the `adapter` is not used here to avoid the error).
-
-```ts filename="middleware.ts"
-import NextAuth from "next-auth"
-import authConfig from "./auth.config"
-
-export const middleware = NextAuth(authConfig).auth
-```
-
-</Accordion>
-</Accordions>
-
 ### Schema
 
 You need to use at least Prisma `2.26.0`. Create a schema file at `prisma/schema.prisma` with the following models.

docs/pages/guides/edge-compatibility.mdx

@@ -67,9 +67,9 @@ export default {
 } satisfies NextAuthConfig
 ```
 
-2. Next, a separate **instantiated** Auth.js instance which imports that configuration, but also adds the adapter.
+2. Next, a separate **instantiated** Auth.js instance which imports that configuration, but also adds the adapter and using `jwt` for the Session strategy:
 
-```ts filename="auth.ts" {2, 10}
+```ts filename="auth.ts" {2, 10, 11}
 import NextAuth from "next-auth"
 import authConfig from "auth.config"
 
@@ -80,6 +80,7 @@ const prisma = new PrismaClient()
 
 export const { handlers, auth, signIn, signOut } = NextAuth({
   adapter: PrismaAdapter(prisma),
+  session: { strategy: "jwt" },
   ...authConfig,
 })
 ```