1da90c2756
### What? [1] Clean up `with-supabase` example following patterns from @leerob's recent video on authentication [2] Add images to matcher to reduce number of times a session is refreshed [3] Move instantiation of `cookieStore` into Supabase server helper ### Why? [1] Make template easier to understand and use [2] Reduce likelihood users will receive Auth Rate Limit Exceeded error [3] Makes creating a Supabase client much simpler in Server Components, Route Handlers and Server Actions ### How? [1] Refactor middleware and its helper function [2] Add image extensions to middleware matcher [3] Call `cookies()` function from `createClient` helper - this should still be in the [same execution context](https://nextjs.org/docs/messages/dynamic-server-error) and appears to work from my testing, but would be good to get the 👍 from someone at Vercel
36 lines
1.1 KiB
TypeScript
36 lines
1.1 KiB
TypeScript
import { createServerClient, type CookieOptions } from "@supabase/ssr";
|
|
import { cookies } from "next/headers";
|
|
|
|
export const createClient = () => {
|
|
const cookieStore = cookies();
|
|
|
|
return createServerClient(
|
|
process.env.NEXT_PUBLIC_SUPABASE_URL!,
|
|
process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
|
|
{
|
|
cookies: {
|
|
get(name: string) {
|
|
return cookieStore.get(name)?.value;
|
|
},
|
|
set(name: string, value: string, options: CookieOptions) {
|
|
try {
|
|
cookieStore.set({ name, value, ...options });
|
|
} catch (error) {
|
|
// The `set` method was called from a Server Component.
|
|
// This can be ignored if you have middleware refreshing
|
|
// user sessions.
|
|
}
|
|
},
|
|
remove(name: string, options: CookieOptions) {
|
|
try {
|
|
cookieStore.set({ name, value: "", ...options });
|
|
} catch (error) {
|
|
// The `delete` method was called from a Server Component.
|
|
// This can be ignored if you have middleware refreshing
|
|
// user sessions.
|
|
}
|
|
},
|
|
},
|
|
},
|
|
);
|
|
};
|