[Oxide] Add built-in @import
processing support
#11239
Merged
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 adds built-in support for processing and inlining
@import
at-rules, in a way that is compatible with Tailwind's@config
and@tailwind
directives.This removes the need for installing and configuring
postcss-import
, but won't cause any issues in projects that already have it set up.The advantage to using the built-in support provided by this PR is that it will let you place your
@config
and@tailwind
directives anywhere in your CSS file you like, whereas usingpostcss-import
directly forces you to put all of your@import
statements before your@config
and@tailwind
directives.Under the hood we are still using
postcss-import
to handle the actual inlining of the@import
at-rules, but our intention is for this to be an implementation detail and we may migrate to another tool or something custom in the future.