Add support for PostCSS Document nodes
#7291
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
thecrypticace
force-pushed
the
fix/postcss-documents
branch
2 times, most recently
from
36a55d0
to
afb4a9c
Compare
thecrypticace
force-pushed
the
fix/postcss-documents
branch
from
afb4a9c
to
4dc671b
Compare
thecrypticace
changed the title
Document nodes
47 tasks
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.
This is very experimental fix but I think maybe in the right direction. It still needs a good bit of thought.
The short summary is that PostCSS now has an optional
Documentnode that represents a file with multiple disjoint sections to be processed by PostCSS. Previously PostCSS only ever assumed a single root node as did Tailwind. Now, when presented with a document node, we'll run the entire Tailwind plugin over each root node contained in the document.Fixes #7207