Repository navigation
chore: upgrade to Tailwind CSS 4 and daisyUI 5 - #565
Merged
Merged
Conversation
Coverage Report
File CoverageNo changed files found. |
Contributor
Author
sebastienfontaine
force-pushed
the
chore/vite-8
branch
from
October 14, 2026 18:22
22d8b84 to
31547a1
Compare
- Tailwind 4 via @tailwindcss/postcss (autoprefixer no longer needed); tailwind.config.js moved to CSS (@theme, @plugin) - daisyUI 5: same built-in themes (dim default, dark for prefers-dark) and the custom tabee theme in the v5 format - renamed utilities (!important suffix, shrink-0, shadow-xs, rounded-sm, z-1) - removed md:flex-0/flex-0: no-op in Tailwind 3, flex: 0 in Tailwind 4, which collapsed the rule form columns - daisyUI renames: *-bordered removed (default), tabs-border, menu-active - compat layer for the daisyUI 4 form classes (form-control, label, label-text, label-text-alt), full-width fields and tabs, tooltips
sebastienfontaine
force-pushed
the
chore/tailwind-4
branch
from
October 14, 2026 18:23
f104fa3 to
5ae2097
Compare
📦 Extension Build Ready!Version: 📥 Download Extension (tabee.zip)Installation
Status
🤖 Auto-generated by GitHub Actions |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.












Stacked on #564. GitHub will retarget it once the PRs below it are merged.
Changes
@tailwindcss/upgradetool:tailwind.config.jsmoved to CSS (@theme), PostCSS uses@tailwindcss/postcss, andautoprefixeris removed (Tailwind 4 handles prefixes).dimdefault,darkfor prefers-dark) and the customtabeetheme rewritten in the v5@plugin "daisyui/theme"format, with the same colors.!w-4→w-4!,flex-shrink-0→shrink-0,shadow→shadow-sm,rounded→rounded-sm,z-[1]→z-1.ringtoring-3, and changed raw CSSflex-shrink: 0to the invalidshrink: 0in the Spot Search UI.Visual fixes
I compared screenshots of every options page and the side panel, before and after, in several themes. Differences fixed:
md:flex-0did nothing in Tailwind 3 but meansflex: 0in Tailwind 4. Removed (8 places).activetomenu-active.input-bordered/select-bordered/file-input-borderedremoved (bordered by default),tabs-bordered→tabs-border.style.css, for classes removed or restyled in v5:form-control,label,label-text,label-text-alt(about 70 uses), full-width fields insideform-control, equal-width tabs, single-line tooltips. It sits in a cascade layer right after daisyUI's and below Tailwind utilities, so utilities still override it. It can go once the forms move to daisyUI 5'sfieldset/legend.Remaining visual differences (daisyUI 5 design)
valentinetheme was redesigned upstream (lighter pink).tabs-border.Vulnerabilities
npm audit: 0 (the last 7 came from Tailwind 3).Tested
vue-tsc, 226 tests andnpm run buildpass locally.tabee,dim,light,valentine.