Ensure we process Tailwind CSS features when using @reference
#16057
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 fixes an issue where if you only used
@reference
that we didn't process Tailwind CSS features.We have a 'quick bail check', in the PostCSS plugin to quickly bail if we konw that we don't need to handle any Tailwind CSS features. This is useful in Next.js applications where every single CSS file will be passed to the PostCSS plugin.
If you use custom font ins Next.js, each of those fonts will have a CSS file as well.
Before we introduced
@reference
, we used@import "tailwindcss" reference
, which passed the bail check because@import
was being used. Now we have@reference
which wasn't included in the list.This is now solved.
Fixes: #16056
Test plan
Added a failing test that is now failing after the fix.