better-auth

Authentication for a monorepo with Next.js and NestJS is set up by wiring a shared Drizzle-backed configuration across both layers. This enables unified login, signup, and session management with a lazy-auth initialization pattern.

Yes, you can use Drizzle for session management across web and backend. The skill provides a shared adapter that maintains consistent backend state and centralizes session handling for frontend and API layers.

The best way to add OAuth to Next.js and NestJS is using an environment-driven configuration with shared auth clients. This approach standardizes protected routes and OAuth integration across the frontend and backend layers.

Yes, environment-driven configuration is required. The authentication workflow relies on environment variables to initialize the shared auth clients and configure OAuth integration for both web and API layers securely.

Lazy initialization for authentication clients defers the auth setup until it is actually needed during a user request. This pattern streamlines login and signup flows by preventing unnecessary immediate instantiation across frontend and backend environments.

Standardizing authentication across frontend and backend in a monorepo reduces setup time and enhances security practices. It ensures consistent session handling and prevents configuration drift between Next.js and NestJS applications.