feat(turbopack): support merged PostCSS configs - #186
Merged
Merged
Conversation
fireairforce
marked this pull request as draft
August 24, 2026 07:25
fireairforce
force-pushed
the
zoomdong/postcss-config-merged
branch
from
August 24, 2026 07:40
79d47b9 to
9c9823c
Compare
fireairforce
force-pushed
the
zoomdong/postcss-config-merged
branch
from
August 24, 2026 07:51
9c9823c to
4b00998
Compare
fireairforce
marked this pull request as ready for review
August 24, 2026 07:53
This file contains hidden or 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
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.
Summary
postcss.tsimplementation unchangedMotivation
Utoopack integrations need to inject framework PostCSS plugins without suppressing a user-owned
postcss.config.*file. Previously inline config short-circuited config discovery, so the two sources were mutually exclusive.Implementation
The change is isolated to Rust. File-only and inline-only configurations continue through the original executor path. When both sources exist, Rust creates a lightweight virtual config module that resolves the two configs sequentially and concatenates their plugin declarations, then passes that single config to the unchanged runtime executor.
Downstream
Verification
cargo fmt --allandgit diff --checkcargo check -p turbopack-node -p turbopack --libcargo clippy -p turbopack-node -p turbopack --lib -- -D warnings