-
Notifications
You must be signed in to change notification settings - Fork 80
chore(deps): update tailwindcss to v4.*
#6286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6286 +/- ##
=======================================
Coverage 76.22% 76.22%
=======================================
Files 393 393
Lines 19777 19777
Branches 4741 4741
=======================================
Hits 15075 15075
Misses 4702 4702
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@cstns why not to 4.1? |
|
v4 has a hard dependency of node >= v20 while our docs state that we support v18. |
|
We have moved the built containers to nodejs 20 and the tests iirc. NodeJS 18 is now EoL so we really should drop it as dependency, but we need to check (and I need to convert my dev env over). |
|
We're risking breaking things upgrading tailwind to 4.0 without making sure all on-premise installations have also done so. I'm fine with upgrading to 4.0 but we should make it clear that the next release will make node 20 mandatory (and also upgrade the docs) |
|
spoke w @hardillb we can safely upgrade to 4.0, I'll add a changelog request announcing our minimum node version change and one for the docs to update the entry |
|
Changelog request and docs update pr's are in place. |
|
Very nice! Well that opens the door than to V4: https://staticmania.com/blog/tailwind-v4-vs-v3-comparison |
|
@cstns I see you already upgraded to v4.0.0. Why not to the latest? https://github.com/tailwindlabs/tailwindcss/releases PS: We can also look into https://tailwindcss.com/plus/ui-blocks#product-application-ui |
|
I'd love a go at the settings pages with tailwind plus, worth getting in my opinion |
|
I set a hard minimum allowed limit of |
tailwindcss to v3.4.0tailwindcss to v4.*
126e7ef to
86971ef
Compare
41b2bf8 to
fe81c6a
Compare
fe81c6a to
7831fd7
Compare
…r enhanced compatibility
… configuration for cleaner styles and updated features
- Replace flex-shrink-* with shrink-*, flex-grow-* with grow-* - Replace outline-none with outline-hidden - Replace overflow-ellipsis with text-ellipsis - Shift rounded scale to preserve v2 visual sizes: - rounded-xl → rounded-lg - rounded-lg → rounded-md - rounded-md → rounded - rounded → rounded-sm - rounded-sm → rounded-xs
- shadow-lg → shadow-md - shadow-md → shadow - shadow-sm → shadow-xs - shadow (bare) → shadow-sm - drop-shadow-md → drop-shadow
- Migrate remaining flex-grow → grow in Vue templates (71 occurrences) - Migrate remaining flex-shrink → shrink in Vue templates (2 occurrences) - Shift drop-shadow → drop-shadow-sm for v2 visual parity - CSS properties in style sections preserved (flex-grow:, flex-shrink:)
Changes applied by the official Tailwind v4 upgrade tool: - Move !important modifier from prefix to suffix (!prop → prop!) - Update max-w-screen-* to max-w-(--breakpoint-*) - Replace break-words with wrap-break-word
…in `AuditLog` and `AuditLogBrowser` components
…ilwind v4 - Convert $ff-* Sass variables to var(--ff-*) CSS custom properties - Move design tokens to @theme inline block in index.css - Fix media queries to use literal pixel values (CSS vars not supported) - Add --ff-grey-500-20 opacity variant for rgba() replacement
- Remove unused safelist from tailwind.config.js (classes are defined in @layer base) - Remove redundant autoprefixer from postcss.config.js (built into @tailwindcss/postcss)
7831fd7 to
8fcb4ca
Compare
|
Fixed my commit signing :) |
- Delete ff-colors.scss and ff-utility.scss (empty stubs pointing to index.css) - Delete ff-theme-light.scss and ff-theme-dark.scss (abandoned dark mode code) - Remove imports from common.scss, layouts.scss, ui-components/index.scss - Remove sass-loader additionalData that referenced deleted files Removes ~350 lines of dead CSS.
- Move ff-core.scss content into common.scss (consolidate heading styles) - Move ff-components.scss to stylesheets/components/ - Remove ui-components/index.scss import from main.js - Remove dead imports from IconLink.vue and ApplicationSummaryLabel.vue - Delete ui-components/stylesheets/ directory All SCSS is now under frontend/src/stylesheets/.
node-sass is deprecated. Dart Sass (sass) is the actively maintained drop-in replacement recommended by the Sass team.
- Remove deleted index.scss imports from setup.js and ui-components/index.js - Replace @include truncate with inline CSS in BrokerClient.vue Fixes webpack build errors after SCSS consolidation.

Description
Upgrade Tailwind to latest version.
3.4.0introduced some breaking changes4.*After addressing the breaking changes, I did a quick comparison between production and local, and nothing major appeared to have changed.
Related Issue(s)
Part of #6325
Checklist
flowforge.yml?FlowFuse/helmto update ConfigMap TemplateFlowFuse/CloudProjectto update values for Staging/ProductionLabels
area:migrationlabel