feat: adds cookies.encode
option allowing minimal cookie sizes
#126
+85
−29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds an experimental option
encode
on thecookies
object when usingcreateBrowserClient()
andcreateServerClient()
.If this is set to
tokens-only
then only the user's access token and refresh token will be encoded in the cookies, causing significant cookie size savings, often greater than 50%. It utilizes split session storage inauth-js
, with some trade-offs such as the inability to access theuser
property on thesupabase.auth.getSession()
object in the server. This wasn't supposed to be done anyway, andgetClaims()
is a secure alternative for it.