tanweer919
1d37593102
Wire the AppShell SDK for auth/identity across the CRM, gated behind isShellConfigured() so the existing mock portal + static demo user stay the fallback until the Shell BFF is configured. - providers.tsx: app-wide <AppShellProvider> (auth passed only when Supabase env set) - next.config.ts: transpilePackages + /shell -> BFF rewrite (keeps /api/geo intact) - login: password -> login(), social -> loginWithOAuth(), OAuth return -> completeOAuthLogin() - register: email/password sign-ups call register() on finish - dashboard: AuthGate bounces unauthenticated visitors; topbar shows ACE identity - docs/APPSHELL_INTEGRATION.md, .env.local.example, .npmrc for GitHub Packages
30 lines
1.1 KiB
TypeScript
30 lines
1.1 KiB
TypeScript
"use client";
|
|
|
|
// AppShell runs in the browser (boot, React context), so the provider is a
|
|
// Client Component. When Supabase env is NOT configured (no BFF yet) we mount the
|
|
// provider WITHOUT `auth` — `useAuth()` still works (returns nulls / status
|
|
// "unauthenticated"), and the existing mock portal remains the fallback. Once the
|
|
// env is set + the Shell BFF is deployed, real auth flows through appshell-sdk.
|
|
|
|
import { AppShellProvider } from "@abe-kap/appshell-sdk/react";
|
|
import type { AppShellOptions } from "@abe-kap/appshell-sdk";
|
|
import type { ReactNode } from "react";
|
|
|
|
const supabaseUrl = process.env.NEXT_PUBLIC_SUPABASE_URL;
|
|
const bffBaseUrl = process.env.NEXT_PUBLIC_BFF_BASE_URL ?? "/shell";
|
|
|
|
const options: AppShellOptions = supabaseUrl
|
|
? {
|
|
auth: {
|
|
supabaseUrl,
|
|
supabaseAnonKey: process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY ?? "",
|
|
appId: "crm-web",
|
|
},
|
|
bffBaseUrl,
|
|
}
|
|
: { bffBaseUrl };
|
|
|
|
export function Providers({ children }: { children: ReactNode }) {
|
|
return <AppShellProvider options={options}>{children}</AppShellProvider>;
|
|
}
|