-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Bump tailwind from 3.4.17 to 4.1.11 #8709
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: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8709 +/- ##
=======================================
Coverage 99.11% 99.11%
=======================================
Files 141 141
Lines 4074 4074
=======================================
Hits 4038 4038
Misses 36 36 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
11c4e9e
to
4d2b2d1
Compare
5e6685d
to
99c9780
Compare
e8154c9
to
7b44d57
Compare
16a5e61
to
2916f72
Compare
2916f72
to
e131141
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just Tested! Worked for me.
e131141
to
5bf67d5
Compare
5bf67d5
to
92fd144
Compare
Hello, thanks for the heads up From the documentation and from your comment at rails/tailwindcss-rails#554 (comment) I understand that
It looks like it is mandatory to import in 8000 the main application.css, which is not what we want here (css files should be separated, we don't want to mix activeadmin and application styles: application may not even use tailwind) At the moment, activeadmin does not even use tailwindcss-rails and I'm not in the position to make this change, but it would be interesting to see how this new feature can help here. Can you fork and make the changes on top of this branch, so I can take a look? |
That is what I am looking for: specific scenarios to trial this experimental approach. Let me think a bit, I'll get back to you. |
- Remove tailwind v3 downgrade from test-application - Use tailwind cli to compile css - Delete generated files that are not used - Add a reference to old javascript config file - Remove `@tailwind` directive - Remove config argument when adding `build:css` script to test app - Rename deprecated utilities https://tailwindcss.com/docs/upgrade-guide#renamed-utilities
Use v4's `scheme-dark` to fix icon colors on some native inputs Ref: https://v3.tailwindcss.com/docs/v4-beta#color-scheme-utilities
92fd144
to
ecfd8a2
Compare
I know there are still discussions over that PR, but it would be nice to have a first iteration of the support merged so we can use it with apps with tailwind v4... Can we help achieve this? |
@tailwind
directivebuild:css
script to test appTODO:
"type": "module",
to app'spackage.json
? 3bfb95e#r1972531187Not from scratch, this is being done by cssbundling railstailwindcss@cli
should be installed as a dev dependency?Additionally:
scheme-dark
on input fields when dark mode is enabledBefore
After