Questions about the future plans

[evgeny1q]

Hi, guys! Thank you for putting so much efforts into this lib! I've seen lots of changes recently on v0.11+ and have some questions on it and your future plans:

1. I have noticed that there are lots of core theme changes - both styles and the way how the themes are merged. Do you have any plan/feeling when you will mark this lib as released - not pre-release one? Couple of releases away or not even on the horizon? Trying to estimate how many changes there could be in the nearest future.

2. Noticed that a type that we used on a project - CustomFlowbiteTheme - disappeared from the core and only accessible from 'flowbite-react/types' now - is this a plan and we can do the migration or it's a mistake and make sense to wait a bit for it to be returned back?

Thank you so much!

PS: I've seen some question about the release asked previously at the end of the last year - maybe any updates?

[SutuSebastian]

Hey there, thanks for the support first of all!

To answer ur questions:

1. I have noticed that there are lots of core theme changes - both styles and the way how the themes are merged. Do you have any plan/feeling when you will mark this lib as released - not pre-release one? Couple of releases away or not even on the horizon? Trying to estimate how many changes there could be in the nearest future.

Before the 0.11.x version the theming system was very limited, it had bad performance and not flexible at all. The 0.11.x brought a brand new core/engine if I can call it that, that basically unlocks that flexibility we've all been asking for, fixes the performance and allows multiple ways of merging/replacing/clearing the component's themes with a fairly complex system, caching layers, all documented in the Theme Docs Page.

This also was a good opportunity for a massive revamp of all the components theme structure and color overrides.

When will this be released as v1 production ready? Good question. In my opinion we're lacking the following for that to happen:

• usage of a headless library like RAC (React Aria Components)
• be on par with all components available in vanilla Flowbite
• export all primitives from a component:
  • hooks (eg: business logic, if any)
  • UI
• improved documentation per component:
  • general usage
  • anatomy
  • examples

All in all, the new core/engine and the theming system can be considered stable and ready for v1, so we're not expecting that many (breaking) changes in that area. As for the ones mentioned above, we will break things.

2. Noticed that a type that we used on a project - CustomFlowbiteTheme - disappeared from the core and only accessible from 'flowbite-react/types' now - is this a plan and we can do the migration or it's a mistake and make sense to wait a bit for it to be returned back?

It's just a simple export change of path, nothing too fancy, but nevertheless we encourage to use the new createTheme() API that is type-safe and has IDE intellisense (see docs), Tailwind CSS formatting and linting (see Editor Setup)

In between life and work, I strive to bring this project/library to a stable and production version, build an ecosystem around it and save tons of hours of redundant work for the community consuming it.