fix: allow cookies encode without getAll/setAll on browser client#213
Merged
Conversation
grdsdev
approved these changes
May 7, 2026
mandarini
pushed a commit
that referenced
this pull request
May 7, 2026
🤖 I have created a release *beep* *boop* --- ## [0.10.3](v0.10.2...v0.10.3) (2026-05-07) ### Bug Fixes * allow cookies encode without getAll/setAll on browser client ([#213](#213)) ([89f3f28](89f3f28)), closes [#170](#170) * enable tree-shaking for browser bundles ([#216](#216)) ([f009d71](f009d71)) * **tsconfig:** set explicit rootDir to silence TS6059 in consumer IDEs ([#211](#211)) ([a77ee8a](a77ee8a)), closes [#209](#209) * validate base64-prefixed chunked cookies decode to valid JSON ([#210](#210)) ([302cc0e](302cc0e)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: supabase-releaser[bot] <223506987+supabase-releaser[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
createBrowserClientalready falls back todocument.cookiewhencookiesis omitted, butencodelives on thecookiesobject, so opting intotokens-onlyforced users to redeclaregetAll/setAll(or pass no-op stubs that would break auth). The types were stricter than the runtime.getAllandsetAllare now optional onCookieMethodsBrowser. When both are omitted in a browser, the same document.cookie fallback is used.CookieMethodsServeris unchanged (no document.cookie there). The deprecatedget/set/removeoverload and the partial-omission case (only one of getAll/setAll provided) keep their existing behavior.Closes #170