Skip to content
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

Update to Tailwind CSS v3.1.8 #186

Merged
merged 1 commit into from
Aug 9, 2022
Merged

Update to Tailwind CSS v3.1.8 #186

merged 1 commit into from
Aug 9, 2022

Conversation

TastyPi
Copy link
Contributor

@TastyPi TastyPi commented Aug 8, 2022

I need the fix in tailwindlabs/tailwindcss#8687 which was released in v3.1.4.

Has there been any thought in decoupling tailwindcss-rails releases from Tailwind? It would be nice to be able to use the latest Tailwind release without having to wait for tailwindcss-rails to be released.

Copy link
Member

@flavorjones flavorjones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@flavorjones
Copy link
Member

@TastyPi Thanks for submitting this. You're asking a good question about decoupling, and I think we're optimizing for the user experience over latest-and-greatest version with the current setup.

Would you mind opening a new issue to start a conversation about supporting folks who have tailwindcss already installed on their system?

@TastyPi
Copy link
Contributor Author

TastyPi commented Aug 9, 2022

@flavorjones Thanks for the review, I've opened #187 to continue that discussion.

@dhh dhh merged commit 60ceae9 into rails:main Aug 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants