Update README.md (Tailwind Specificity Conflicts) #254
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
Add note about tailwind specificity conflicts
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Maybe better to link to #109 (comment) as I saw @vladmoroz just mentioned this in response to an issue w/ tailwind. |
|
Hey, thanks for looking into it. We decided to wait for a new Tailwind release first and add a note in the docs to upgrade it once it's out. For now I'll keep replying to the related issues and pointing to the comment with the resolution. |
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.
Add note about tailwind specificity conflicts as there seems to be a lot of issues created in relation to this. Hopefully it will stop unnecessary issues until the fix is released!