-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Upgrade lightningcss to 1.30.0
#17979
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
philipp-spiess
commented
May 12, 2025
•
edited
Loading
edited
- Fixes #17556
a40dfd5
to
779f2fb
Compare
779f2fb
to
3c0d44c
Compare
1.20.0
1.30.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small question, I wonder why some of the rules are split right now.
Can you also add a changelog entry?
.shadow-xl { | ||
box-shadow: var(--tw-inset-shadow), var(--tw-inset-ring-shadow), var(--tw-ring-offset-shadow), var(--tw-ring-shadow), var(--tw-shadow); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, what happened here 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fixing an issue in ordering where previously the --tw-shadow
could sometimes appear after the box-shadow
assignment because of how @supports
was resolved. This generates more code now but it's corrent in a sense that even if the supports query works, the assignment is in the right order still.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah that's fair, just an interesting change. I would be smaller again if we didn't have the @supports
but this is fine (and correct) so let's merge it!