This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
fix compatibility with tailwind v2 #14
Closed
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
|
Hi @darkyzhou, thank you very much for taking the time to create this PR, and I'm sorry for taking so long to address it. I'm actually deprecating this plugin, since the |
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The changes are tested to have #12 fixed.
However, Tailwind CSS v2 will still complain:
This is because according to tailwindlabs/tailwindcss#2571, Tailwind CSS v2.0 no longer supports IE11. I suggest bumping the package's version and claim that the new version should only be used with Tailwind CSS v2.0, dropping the support for IE11.
Or...merge the changes, keeping the support for IE11?