feat(dev): stabilize PostCSS and Tailwind options #5960
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.
In order to reduce the number of unstable flags before the v2 release, this adds new top-level
postcss
andtailwind
config options, the same as those introduced in the v2 branch. The difference is that in v2 these are enabled by default to provide an opt-out, but this PR adds them to v1 disabled by default to provide an opt-in.To reduce unnecessary API churn before the v2 release, the existing
unstable_postcss
andunstable_tailwind
future flags are still supported but marked as deprecated via JSDoc comments. Deprecation warnings are also logged to the terminal if either of them are used.