fix: allow use of createBrowserClient
without window
present
#20
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.
Allows calling
createBrowserClient
without throwing an error when not in a browser context (i.e.window
is missing).This is especially useful when using in Next.js Pre-Rendering mode where the client's non-
auth
namespaces could be useful, such as to load public data from PostgREST.If however the
auth
namespace is used, thesetAll
handler function will throw an error indicating to the user that they're doing something wrong. This shouldn't come up in Pre-Rendering mode ever.See: https:/orgs/supabase/discussions/27037#discussioncomment-9852948