Hey everyone,
Thanks for the feedback.
Unfortunately it’s a pure
CSS+JavaScriptlibrary with lots of amazing components and guides. The linkedPhoenixproject is based on version1.6.x.People reading your post could expect few things:
…
I am aware of this, however, the guide is there to showcase how it can be used as a JS library, though I would be more than happy to collaborate on creating a native integration with LiveView components - after all Flowbite is also open-source so the components can be ported to any framework or language.
The guide does indeed include a walkthrough for pre-v1.7 versions of Phoenix, but the guide also states that you can skip the Tailwind CSS installation part if you have v1.7 or later. The other parts of the guide are relevant and are tested with Phoenix v1.7.
Hey Zoltán, welcome.
Personally I’m using Daisy now, as it has not JS and thus plays very nicely with LV.
Flowbite could be interesting as it is more powerful (thanks to JS).
Didn’t read your guide yet, but I wonder how all that JS in flowbite plays with LV?
DaisyUI is great, as far as I am concerned I have found no immediate issues after working a couple of hours with Phoenix (Elixir) and Flowbite, but if problems do arise I am available to provide updates and manage PRs if others want to contribute.
According to his reply on reddit there are no known issues.
I haven’t tested it though.
That is right, for the short term I have found no problems using the two together.
