fix: remove empty :global selector that breaks Lightning CSS #6165
+1
−1
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
.react-datepicker__sr-onlyselector to inside it:global {}block in the CSS modules output when compilingdatepicker-cssmodules.scssRoot Cause
When the
/* sr-only utility class for accessibility */comment was placed as a standalone comment before the.react-datepicker__sr-onlyclass, Sass would wrap it in its own:global {}block in the CSS modules output:Since a comment doesn't count as actual CSS content, this resulted in an empty selector block that Lightning CSS rejects.
Test plan
yarn buildcompletes successfully:global {}blocks in generated CSS modules filesFixes #5989
🤖 Generated with Claude Code