clerk-nextjs-patterns

To prevent UI flashes during Next.js authentication conversions, use the server-side `await auth()` API instead of client-side `useAuth` hooks. This approach ensures secure Clerk auth patterns by rendering protected content directly on the server without exposing undefined authentication states.

The best way to protect Next.js Server Actions and API routes with Clerk is to verify user sessions using awaited server APIs. Implement proper 401/403 HTTP status semantics to handle unauthorized access and enforce route authorization before executing action logic.

You can configure Next.js middleware to protect dashboard routes by defining route matchers and applying a protected-first or public-first middleware strategy. This Clerk setup ensures pending session tasks are handled correctly and unauthorized users are redirected before rendering.

Next.js caching leaks user data across sessions when cache keys lack proper user scoping. To prevent cross-user data leaks with Clerk, you must generate cache keys that include the `userId` or `orgId` and implement strict revalidation strategies tied to the authenticated session.

To generate a custom JWT token for external APIs like Hasura, use the Clerk `getToken` or `verifyToken` server APIs within your Next.js application. This provides a secure authentication pattern to authorize requests to external services.