Double checking things and letting Gemini make some notes.
This commit is contained in:
@@ -46,3 +46,17 @@ A detailed, step-by-step plan for migrating SkeletonLabs from v3 to v4, specific
|
||||
5. **Run `npm run build` and `npm run dev`** to verify the build and functionality.
|
||||
6. **Replace `Modal` components:** Update existing components that used an older `<Modal>` (e.g., from `flowbite-svelte` or previous custom efforts) with Skeleton's new `Dialog` component.
|
||||
7. **Address Svelte 5 reactivity warnings:** Fix any warnings related to data handling or non-reactive updates.
|
||||
|
||||
## Final Decision (2025-12-08)
|
||||
|
||||
**Outcome:** Abandoning SkeletonLabs.
|
||||
|
||||
**Reasoning:**
|
||||
Despite following the official migration guide and attempting various configurations, the upgrade from SkeletonLabs v3 to v4.7.4 consistently fails with a blocking build error: `[@tailwindcss/vite:generate:build] Cannot use @variant with unknown variant: md`. This error points to a fundamental incompatibility between SkeletonLabs' pre-compiled CSS and the Tailwind CSS v4 build process in this Vite project.
|
||||
|
||||
Given the significant time spent debugging this issue without a clear resolution path through configuration, the most pragmatic decision is to remove SkeletonLabs entirely and proceed with custom UI component implementation.
|
||||
|
||||
**Path Forward:**
|
||||
1. All SkeletonLabs dependencies (`@skeletonlabs/skeleton`, `@skeletonlabs/skeleton-svelte`) will be removed from `package.json`.
|
||||
2. All SkeletonLabs configurations (e.g., in `tailwind.config.ts`, `app.css`) will be removed.
|
||||
3. UI components previously provided by SkeletonLabs will be replaced with custom Svelte components styled with pure Tailwind CSS.
|
||||
|
||||
Reference in New Issue
Block a user