Scott.Idem/OSIT-AE-App-Svelte
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Double checking things and letting Gemini make some notes.

Browse Source
This commit is contained in:
Scott Idem
2025-12-08 17:29:59 -05:00
parent 098fc94a5a
commit 9d5c079935
4 changed files with 66 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
GEMINI_Flowbite_upgrade_2025-12.md
View File

@@ -36,3 +36,16 @@ A clear understanding of Flowbite-Svelte's compatibility with our current stack.
2. **If no compatible version exists or issues persist:**
* **Decision:** Abandon Flowbite-Svelte.
* **Action:** Systematically replace its components with custom-built Svelte/Tailwind components, starting with critical ones like `Modal` (using our `element_modal_v1.svelte` if not using Skeleton's `Dialog`).
## Final Decision (2025-12-08)
**Outcome:** Hold off on upgrading Flowbite-Svelte.
**Reasoning:**
The changelog indicates that experimental Svelte 5 support was added in version `0.45.0`. However, there is no mention of compatibility with Tailwind CSS v4. Since SkeletonLabs (the other major UI library) is being removed due to build failures, our immediate priority is to stabilize the project and replace Skeleton's components. Introducing another potential variable by upgrading Flowbite-Svelte at the same time is not advisable.
**Path Forward:**
1. The currently installed version of `flowbite-svelte` (`1.28.1`) will be kept for now.
2. After SkeletonLabs is removed and the project builds successfully, we will test the functionality of existing Flowbite-Svelte components.
3. If they work, we will continue to use them.
4. If they cause build or runtime errors after SkeletonLabs is removed, we will then evaluate either upgrading to `v0.45.0` (with careful testing against Tailwind v4) or abandoning Flowbite-Svelte and replacing its components with custom ones.