Supabase is an open source Firebase alternative. Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, and Storage.

Supabase

```js
const [user, setUser] = useState();
  useEffect(() => {
    setUser(supabase.auth.user());
  }, []);
```
Had to do this to prevent a NextJs hydration error, but now I have to refresh the page for conditional rendered components to be correct, anyone know a fix?

Hello <@238234312942551040>!
This thread has been automatically created from your message in <#843999948717555735> a ``few seconds ago``.

Pinging <@&951828363943759883> so that they see this as well!

**Want to unsubscribe from this thread?**
Right-click the thread in Discord (or use the ... menu) and select **Leave Thread** to unsubscribe from future updates.

**Want to change the title?**
Use the `/title` command!

**We have solved your problem?**
Click the button below to archive it.

🆕 NextJs hydration error causes another conditional rendering conflict

Originally I just had `const user = supabase.auth.user()`, but since logging out doesn't cause a re-render it caused a hydration error cause of a conditional render

having a usercontext would probably fix this, but any other ideas?

ok my mind is blown <a:mind_blown:767753151024594954> 
if i deploy the app there is no conditional rendering issues or anything

Thread was archived by <@238234312942551040>. Anyone can send a message to unarchive it.

NextJs hydration error causes another conditional rendering conflict