Update to Tailwind CSS v3.1.8 #186
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@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? |
|
@flavorjones Thanks for the review, I've opened #187 to continue that discussion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I need the fix in tailwindlabs/tailwindcss#8687 which was released in v3.1.4.
Has there been any thought in decoupling
tailwindcss-railsreleases from Tailwind? It would be nice to be able to use the latest Tailwind release without having to wait fortailwindcss-railsto be released.