postcss 7 #6
Merged
postcss 7 #6
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
|
What stalled this? Was just playing with tailwindcss and can't use their custom postcss plugin properly without |
|
nothing, rebased and updated to postcss 7 |
|
Works with what I'm doing 👍 |
emilbayes
approved these changes
Jul 16, 2019
|
📦 2.0.0 |
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.
Most postcss plugins now expect postcss 6. I think a lot of them work in both v5 and v6 though because the changes were quite minimal.
This would be a major bump, for those few plugins that do not yet support v6