bug: Flyonui crashes if components runs through ssr

[haexhub]

What version of FlyonUI are you using?

2.1.0

Which browsers are you seeing the problem on?

All browsers

Reproduction URL

https://github.com/haexhub/flyonui-ssr-bug

Describe your issue

Hi
I have a problem using flyonui with nuxt, but it should be the same for every ssr framework.
I am aware that flyonui only works on the client side and needs to be set up accordingly, which I am doing.
However, my app crashes as soon as I only import classes from flyonui.
import { HSOverlay } from “flyonui/flyonui”; is enough to trigger the “error”. Even if nothing is done with it at all.
I have created a demo component (UiDialog). Even if I want to instantiate the class in the mounted hook first. As soon as I wrap everything in a ClientOnly element I can solve this, but it would be nice if flyonui could handle this better.

[github-actions]

Hi @haexhub

Thank you for your support in helping us improve FlyonUI!

We’ve received your submission and will respond within few business days. Our team handles issues one at a time, and we’ll be reviewing yours as soon as possible.

In the meantime, any additional details or a reproducible example would be greatly appreciated and will help us resolve the issue more efficiently.

Thank you for your patience and understanding!

[yagnikvamja]

Hello @haexhub,

Thank you for reporting this issue and for providing a detailed explanation along with a reproduction URL — that’s very helpful.

Currently, FlyonUI is designed to work on the client side only, and does not support server-side rendering (SSR) environments. As a result, importing HSOverlay directly in an SSR context may cause errors due to the lack of access to the window or document objects during server-side rendering.

We recommend wrapping any FlyonUI-dependent components or logic inside Nuxt’s <ClientOnly> wrapper. This ensures proper execution in the browser environment, allowing FlyonUI to initialize and function as expected.

If you have any further questions or suggestions, feel free to reach out!

~Best regards,