bug: vite build warning messages

[pigochu]

What version of FlyonUI are you using?

v1.1.0

Which browsers are you seeing the problem on?

All browsers

Reproduction URL

https://flyonui.com/framework-integrations/laravel/

Describe your issue

I executed npm vite build using the instructions from the following URL and many warning messages occurred
https://flyonui.com/framework-integrations/laravel/

warnings when minifying css:
▲ [WARNING] Unexpected "*" [css-syntax-error]

    <stdin>:6515:76:
      6515 │ ... > .combo-box-selected\:active*:not(ul, .menu-title, .collaps...
           ╵                                  ^


▲ [WARNING] Unexpected "*" [css-syntax-error]

    <stdin>:6535:84:
      6535 │ ...cted .combo-box-selected\:menu*:not(ul, .menu-title, .collaps...
           ╵                                  ^


▲ [WARNING] Unexpected "*" [css-syntax-error]

    <stdin>:6554:76:
      6554 │ ... > .combo-box-selected\:active*:not(ul, .menu-title, .collaps...
           ╵                                  ^


▲ [WARNING] Unexpected "*" [css-syntax-error]

    <stdin>:6574:83:
      6574 │ ...ected.combo-box-selected\:menu*:not(ul, .menu-title, .collaps...

Are these warning messages normal?

[github-actions]

Hi @pigochu

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!

[OmkarOza]

Hello @pigochu,

Thank you for bringing this to our attention. We’ve reviewed the issue and have implemented a fix. The update will be included in the upcoming release, so please stay tuned for that.

~Best regards.

[OmkarOza]

Hello @pigochu,

Thank you for your patience. We have resolved the issue you were experiencing. Please update your package to FlyonUI v1.2.0 and continue using it without any concerns.

Best regards,

[pigochu]

@OmkarOza
I upgrade to 1.2.0 , all input's placeholder and floating label will be hidden
So I downgrade to 1.1.0 , It's works fine .

[OmkarOza]

Hello @pigochu,

In version 1.2.0, we updated the code structure for input components, which may have affected the visibility of placeholders and floating labels. I recommend reviewing the updated structure in our documentation to accommodate these changes. There is no need to downgrade to version 1.1.0. If you encounter any further issues or have questions, please feel free to reach out.

Best regards