-
Notifications
You must be signed in to change notification settings - Fork 93
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
Tailwind CSS v4 support #163
Comments
Yesterday I upgraded my rails app which is running on rails main. I solved everything by adding simply add the two gems in my gem file.
|
tagliala
added a commit
to activeadmin/activeadmin
that referenced
this issue
Jan 26, 2025
On Rails 7.0, lock concurrent-ruby to 1.3.4 to address rails/rails#54260 Rails 7.0 bundle has been updated with 3.3.x: ``` rvm use 3.3.6 do bash -c "BUNDLE_GEMFILE=gemfiles/rails_70/Gemfile bundle update" ``` Additionally, add a workaround to make sure that the test application uses Tailwind v3. The current cssbundling-rails approach Close #8611 Ref: rails/cssbundling-rails#163
tagliala
added a commit
to activeadmin/activeadmin
that referenced
this issue
Jan 26, 2025
On Rails 7.0, lock concurrent-ruby to 1.3.4 to address rails/rails#54260 Rails 7.0 bundle has been updated with 3.3.x: ``` rvm use 3.3.6 do bash -c "BUNDLE_GEMFILE=gemfiles/rails_70/Gemfile bundle update" ``` Additionally, add a workaround to make sure that the test application uses Tailwind v3. The current cssbundling-rails approach Close #8611 Ref: rails/cssbundling-rails#163
tagliala
added a commit
to activeadmin/activeadmin
that referenced
this issue
Jan 26, 2025
On Rails 7.0, lock concurrent-ruby to 1.3.4 to address rails/rails#54260 Rails 7.0 bundle has been updated with 3.3.x: ``` rvm use 3.3.6 do bash -c "BUNDLE_GEMFILE=gemfiles/rails_70/Gemfile bundle update" ``` Additionally, add a workaround to make sure that the test application uses Tailwind v3. The current cssbundling-rails approach Close #8611 Ref: rails/cssbundling-rails#163
tagliala
added a commit
to activeadmin/activeadmin
that referenced
this issue
Jan 26, 2025
On Rails 7.0, lock concurrent-ruby to 1.3.4 to address rails/rails#54260 Rails 7.0 bundle has been updated with 3.3.x: ``` rvm use 3.3.6 do bash -c "BUNDLE_GEMFILE=gemfiles/rails_70/Gemfile bundle update" ``` Additionally, add a workaround to make sure that the test application uses Tailwind v3. The current cssbundling-rails approach Close #8611 Ref: rails/cssbundling-rails#163
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running
rails new my_app -c tailwind
results in the following for me (rails 8.0.1
/ruby 3.4.1
):It looks like there are a few things to update to get full v4 support:
tailwind.config.js
file@import
statements inapplication.tailwind.css
The text was updated successfully, but these errors were encountered: