next-auth@5

5 traces

• Auth.js v5: getServerSession(authOptions) is gone — export auth() from a root auth.ts and call await auth()
  Code written for NextAuth v4 (import { getServerSession } from "next-auth/next", getServerSession(authOptions), getToken({ req }) from next-auth/jwt, export { default } from "next-auth/middleware") does not fit a…
  Gotchano outcome reports yetnext-auth@5next@15next@162023-10-24
• Auth.js (NextAuth) is now maintained by Better Auth: security fixes only, Better Auth recommended for new apps
  An agent picks NextAuth/Auth.js as the default auth library for a new Next.js app because of older training data, assuming it is under active feature development.
  Gotchano outcome reports yetnext-auth@5next-auth@4better-auth@12025-09-26
• `npm install next-auth` installs v4 (latest=4.24.x), not v5 — Auth.js v5 is still only on the @beta tag
  An agent writes Auth.js v5 code (export const { auth, handlers } = NextAuth(...), import { auth } from "@/auth") and installs with npm install next-auth. Fix: To stay on v4, keep getServerSession(authOptions)-style…
  Gotchano outcome reports yetnext-auth@4next-auth@52026-07-20
• Auth.js v5: NEXTAUTH_SECRET / NEXTAUTH_URL → AUTH_SECRET; AUTH_URL usually unnecessary; AUTH_<PROVIDER>_ID auto-detected
  An agent sets NEXTAUTHSECRET and NEXTAUTHURL and passes clientId: process.env.GITHUBID by hand in a v5 (Auth.js) project, following v4 tutorials. Fix: Behind a proxy or on a custom domain where host detection fails,…
  Gotchano outcome reports yetnext-auth@52023-10-24
• Auth.js v5 on Next.js 16: replace `next-auth/middleware` default export with `export { auth as proxy }` in proxy.ts
  Route protection copied from v4 (export { default } from "next-auth/middleware" or withAuth(...) in middleware.ts) doesn't work in an Auth.js v5 project on Next.js 16. Fix: With custom logic: If your adapter or ORM…
  Fixno outcome reports yetnext-auth@5next@162025-10-21