LukeParke/better-auth
1
0
Fork 0
mirror of https://github.com/LukeHagar/better-auth.git synced 2025-12-09 12:27:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update cookie caching section for clarity and framework naming

Browse Source
This commit is contained in:
Bereket Engida
2025-05-07 09:07:38 -07:00
parent defadb3b72
commit 4c106d20e3
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/content/docs/guides/optimizing-for-performance.mdx
View File

@@ -11,7 +11,7 @@ Caching is a powerful technique that can significantly improve the performance o
### Cookie Cache
Calling your database every time `useSession` or `getSession` invoked isn’t ideal, especially if sessions don’t change frequently. Cookie caching handles this by storing session data in a short-lived, signed cookie—similar to how JWT access tokens are used with refresh tokens.
Calling your database every time `useSession` or `getSession` invoked isn’t ideal, especially if sessions don’t change frequently. Cookie caching handles this by storing session data in a short-lived, signed cookie similar to how JWT access tokens are used with refresh tokens.
To turn on cookie caching, just set `session.cookieCache` in your auth config:
@@ -34,8 +34,8 @@ Read more about [cookie caching](/docs/concepts/session-management#cookie-cache)
Here are examples of how you can do caching in different frameworks and environments:
<Tabs items={["Next.js", "Remix", "SolidStart", "React Query"]}>
<Tab value="NextJS">
<Tabs items={["Next", "Remix", "SolidStart", "React Query"]}>
<Tab value="Next">
Since Next v15, we can use the `"use cache"` directive to cache the response of a server function.
```ts