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 PR does a few things:
1. refactors
mergeSelectors
to merge only consecutive selectorsPreviously it was merging classes across whole generated results. This was changing the order of some utilities and cause some issues like #1967 and #1978.
I tested the merge behaviour with cssnano, esbuild, and lightningcss. As far as I see, they are all only merging the consecutive selectors. I don't even know why we have this feature though.
2. Consistent sorting
I made some improvements to our sorting logic. These improvements are bringing it closer to the output of Tailwind. But they caused some mergeable selectors to be rendered far from each other. To fix that, I needed to make more changes.
Roughly sorting changes are: