Type Alias CookieMethodsBrowser

If set to true, only the user's session (access and refresh tokens) will be encoded in cookies. The user object will be encoded in local storage if the userStorage option is not provided when creating the client.

You should keep this option the same between createBrowserClient() and createServerClient(). When set to tokens-only accessing the user property on the data returned from getSession() will only be possible if the user has already been stored in the separate storage. It's best to use getClaims() instead to avoid surprises.

Required when reading cookies from a custom store. If both getAll and setAll are omitted in a browser runtime, the client falls back to reading via document.cookie. Tokens and PKCE code verifiers are still persisted in cookies regardless of the encode option, so cookie access (custom or fallback) is required for auth to work.

Required alongside getAll when using a custom cookie store. If both getAll and setAll are omitted in a browser runtime, the client falls back to writing via document.cookie.