blade-better-auth

import { betterAuth } from 'better-auth'; import { ronin } from "blade-better-auth"; import { createSyntaxFactory } from 'blade-client'; // --- Option 1: Use the default RONIN client managed by the adapter --- // This simplifies setup, assuming a default RONIN environment and config. const authWithDefaultClient = betterAuth({ database: ronin(), // Use the default RONIN client // ... other Better Auth configuration, e.g., providers, secrets secret: process.env.AUTH_SECRET ?? 'super-secret-dev-key', // Example secret for development callbacks: { async signIn({ user }) { console.log(`User ${user.email} signed in.`); return true; }, }, }); // --- Option 2: Provide a custom RONIN client instance --- // Useful for specific configurations, e.g., custom tokens, endpoints, or advanced client options. const customClient = createSyntaxFactory({ token: process.env.RONIN_TOKEN ?? '', // Ensure RONIN_TOKEN is set in environment for production // ... other blade-client configuration specific to your RONIN setup }); const authWithCustomClient = betterAuth({ database: ronin(customClient), // Pass the custom client instance // ... other Better Auth configuration secret: process.env.AUTH_SECRET ?? 'another-secret-dev-key', callbacks: { async redirect({ url, baseUrl }) { console.log(`Redirecting to ${url} from ${baseUrl}.`); return url; }, }, }); console.log('Better Auth adapters initialized for different client types.'); // In a real application, you would typically export and use one of these instances // within your API routes, server-side functions, or authentication middleware. // export { authWithDefaultClient as auth };