Joe

It seems adding the following event forces the session to refresh. ```js const event = new Event('visibilitychange'); document.dispatchEvent(event); ``` If I add this right before redirecting, it seems to work...

Any updates on this?

I agree, if the command works fine why is there a warning? I am not sure I even understand what the error is trying to say. Still seeing this with...

I can confirm this is still an issue.

I am getting the same error while using turborepo with npm and nextjs. My dependencies are installing but when I start the dev server I see the following. ``` 0...

Having the same issue with `Golos_Text`

Also having this issue, I am using a custom toast and using the Headless UI `` component. ```ts const showSuccessToast = () => toast.custom( (t) => ( Successfully updated role...

Any updates on this? I still get the error :/

> Not a fix for the hydration error, but if you are just doing this “isMounted” workaround to implement dark mode, there is an easy alternative. > > just use...

I'm also pretty confused about the best way to fix this. I simply want the viewport to show underneath the trigger.