// supabase-auth-server.ts: the other way, with Supabase Auth holding your users. Server side. // npm install @supabase/supabase-js @supabase/ssr // @supabase/ssr keeps the Supabase session in cookies, so your server can read who is signed in. // This uses the PUBLISHABLE key (sb_publishable_...): the browser has it too, and RLS policies decide what each user may touch. import { createServerClient, parseCookieHeader, serializeCookieHeader } from '@supabase/ssr'; /** A Supabase client for one request. Cookies it refreshes are written to `responseHeaders`. */ export function supabaseFor(request: Request, responseHeaders: Headers) { return createServerClient(process.env.SUPABASE_URL!, process.env.SUPABASE_PUBLISHABLE_KEY!, { cookies: { getAll() { return parseCookieHeader(request.headers.get('cookie') ?? '').map(({ name, value }) => ({ name, value: value ?? '' })); }, setAll(cookiesToSet, headers) { for (const { name, value, options } of cookiesToSet) { responseHeaders.append('set-cookie', serializeCookieHeader(name, value, options)); } // Cache headers from Supabase, so a CDN never stores a response that sets someone's session cookie. for (const [key, value] of Object.entries(headers)) responseHeaders.set(key, value); }, }, }); } /** * The signed-in user's id, or null. getClaims() checks the token's signature, so it is safe to trust on the server. * Never trust getSession() on the server: it reads the cookie without checking it again. */ export async function currentUserId(request: Request, responseHeaders: Headers): Promise { const { data, error } = await supabaseFor(request, responseHeaders).auth.getClaims(); if (error || !data) return null; return data.claims.sub; }