You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a library author, I want control over the variable names exposed in my compiled stylesheet. Especially when applications might already be using lightningcss themselves for the final bundle.
Would it be possible to allow changing the prefix?
But they are not your variables, they are lightningcss variables. I think it's important that two libraries/files compiled independently by lightningcss can interact as expected. For example if some file sets color-scheme: light and another sets color-scheme: dark, the same variable names should be used to correctly emulate browser behavior. If each library uses its own variables, these won't necessarily line up.
Are you running into a real issue here or just a preference?
The
light-dark()
transform generates these variables:As a library author, I want control over the variable names exposed in my compiled stylesheet. Especially when applications might already be using
lightningcss
themselves for the final bundle.Would it be possible to allow changing the prefix?
If not out-of-the-box, then maybe through a custom transform?
The text was updated successfully, but these errors were encountered: