Tailwind v4 css configuration #8649
Conversation
This reverts commit 3bfb95e.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8649 +/- ##
=======================================
Coverage 99.11% 99.11%
=======================================
Files 141 141
Lines 4073 4073
=======================================
Hits 4037 4037
Misses 36 36 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@mgrunberg Would the configuration be simplified if the view files were published in the NPM package, similar to what #8220 was trying to achieve? I think that would remove the need for the |
@hasghari Thanks for the contribution, but I'm not ready to reopen the #8220 discussion. That's why I'm still referencing gem files. Speaking about simplicity, I do have the idea of reducing the usage of |
|
Hey! I've successfully moved to tailwind v4 by having both javascript and css configurations within the same setup. Full configuration is here: https://gist.github.com/amkisko/af1b2f7dc4f0f941437ea16400277864 The idea is to use "old" way with custom rake task and javascript configuration file for resolving dynamic paths in pair with |
Built on top of #8640
Exploring an idea to move from javascript config to CSS config.
Pros: Use the latest tailwind configuration mechanism (clean IMO).
Cons: There won't be a single way to configure tailwind.