nextjs-better-auth-session-guard

Real-time session invalidation in Next.js requires a dual-layer approach combining a server-side initial check with a client-side SessionGuard component that monitors the Better Auth useSession hook for runtime changes.

Protected content remains visible after sign out when relying solely on server-side checks; adding a client-side SessionGuard using the Better Auth useSession hook ensures invalid sessions are detected across tabs and redirects occur immediately.

Configure Better Auth client polling for session changes by enabling fetchOnWindowFocus, fetchOnReconnect, and setting a configurable refetchInterval to ensure the client detects session invalidation across browser tabs and after page reloads.

Yes, this real-time session guard approach works with E2E tests by supporting verifications of session persistence and sign out behavior, while preserving return URLs and avoiding unnecessary loading spinners during redirects.

You need a client-side SessionGuard component for Next.js authentication when server-side initial checks are sufficient for loading but you must detect runtime session changes, such as sign-outs occurring in other tabs or after page reloads.