fix: css/global not handle the exports name #18341
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.
According the definition of the css/global and css module type, css/global should handle the exports name, css shouldn't, but now is reversed, this PR aimed to fix that.
Besides that, this PR also does:
@keyframe
and@property
should keep it as is in css/global:export
is a css/global css/module feature, so remove it from css generator optionsWhat kind of change does this PR introduce?
Did you add tests for your changes?
updated snapshot
Does this PR introduce a breaking change?
yes, exportsConvention is remove from css generator options
What needs to be documented once your changes are merged?
update css generator options